/// ------------------------------------------------------------------------------------
/// <summary>
/// Probably unused, but we'll put something in because a window is probably 'something'
/// and therefore interesting to the TestCollectorEnv.
/// </summary>
/// <param name="_ew"></param>
/// <param name="dmpAscent"></param>
/// <param name="fJustifyRight"></param>
/// <param name="fAutoShow"></param>
/// ------------------------------------------------------------------------------------
public void AddWindow(IVwEmbeddedWindow _ew, int dmpAscent, bool fJustifyRight,
bool fAutoShow)
{
AddResultString("A window");
}
/// <summary>
/// Add a display region whose contents are controlled by the client, which must
/// implement <c>IVwEmbeddedWindow</c>. The mechanism is designed to allow either an
/// embedded window (which gets moves as the view is laid out) or just a region of
/// the larger window which the client draws into.
/// ENHANCE JohnT: can this be implemented reliably? What if the root box is displayed
/// in two places, so we can't just move the embedded Window? (Could we say that it
/// appears in the primary split? Which one is primary?)
/// </summary>
/// <param name="_ew"/><param name="dmpAscent">Distance from top of embedded box to baseline for text alignment </param><param name="fJustifyRight">True if embedded box is last in para and should be rightaligned,
/// as we do with "..." buttons in data entry. (However, that facility is currently
/// implemented a different way). </param><param name="fAutoShow">True if true view will ensure visibility before drawing.
/// <h3>Note</h3> This method is not yet implemented. </param>
public void AddWindow(IVwEmbeddedWindow _ew, int dmpAscent, bool fJustifyRight, bool fAutoShow)
{
throw new NotImplementedException();
}
public void AddWindow(IVwEmbeddedWindow _ew, int dmpAscent, bool fJustifyRight, bool fAutoShow)
{
throw new NotImplementedException();
}
