(Windows only; GUI for .NET only)
A control container that allows you to embed the client area of an ABL window for display
in a .NET form. When added to a .NET form, this container allows the embedded ABL client
area to appear as though it is added directly to the client area of the .NET form. This
allows the widgets in the ABL client area to be displayed in the .NET form, but also allows
you to interact with these widgets much as if they were still displayed in the original ABL
PUBLIC WindowContainer ( )
System.Windows.Forms.UserControl class (from the .NET Framework)
This class does not implement interfaces (beyond those it inherits from its base
This class does not contain methods (beyond those it inherits from its base class).
This class does not contain events (beyond those it inherits from its base class).
- To embed the client area of an ABL window in a .NET form, set the
EmbeddedWindow property of the WindowContainer to the
handle of the ABL window and add the WindowContainer to a Progress.Windows.Form class instance. For more information on how ABL
supports the behavior of the ABL window and its client area embedded in a form using a
Progress.Windows.WindowContainer, see the EmbeddedWindow property reference entry.
- You can use multiple instances of this class to embed the client areas of one or more
ABL windows in the client area of any single .NET form. However, a
Progress.Windows.MDIChildForm is designed to embed the client area of
only one ABL window that you associate with the object. For more information, see the
Progress.Windows.MDIChildForm class reference entry.
- The menus from an embedded ABL window are not added to any form to which you add the
WindowContainer. You must add any associated menu or toolbar
functionality to the form using corresponding .NET controls.
- For any WindowContainer that you add to a
Progress.Windows.Form, you must programmatically resize and reposition
the WindowContainer to fit the client area of the form as it is being
- When you embed the client area of an ABL window in a form, the window and its widgets do
not interact directly with other .NET controls that may be added to the form. This means,
for example, the embedded client area does not participate in the tab order of the form.
Thus, there is no way to tab into the embedded client area from another .NET control or
WindowContainer, and there is no way to tab out of the embedded client area into another
.NET control or WindowContainer. All tabbing within an embedded client
area stays within the WindowContainer where it is embedded.
- The AVM passes all unhandled keystrokes in an embedded ABL client area to the form that
contains it. This means that you can interact with menus and use menu and toolbar
accelerator keys even when focus is on the embedded client area.