Applies to:
|
BROWSE widget (browse and column), BUTTON widget, COMBO-BOX widget, CONTROL-FRAME widget, DIALOG-BOX widget, EDITOR widget, FIELD-GROUP widget, FILL-IN widget, FRAME widget, IMAGE widget, LITERAL widget, MENU-ITEM widget, RADIO-SET widget, RECTANGLE widget, SELECTION-LIST widget, SLIDER widget, SUB-MENU widget, TEXT widget, TOGGLE-BOX widget, SHADOW-WINDOW widget, WINDOW widget
|
However, .NET form families exhibit one feature that ABL window families do not share—child forms never appear behind the parent form. The reason is that ABL window family behavior results from a native OpenEdge implementation that is different from the feature provided by Windows. In an ABL session, the .NET form and ABL window family mechanisms continue to work differently for forms and windows as long as .NET forms only parent forms and ABL windows only parent windows.
However, you can also parent .NET forms and ABL windows to each other using the PARENT attribute on the shadow window of a .NET form or the PARENT attribute on an ABL window. You can obtain the handle to the shadow window of a .NET form that you want to be a child or a parent from the value of the ProWinHandle property on the form (provided by Progress.Windows.Form). Then:
When you establish parent/child relationships like this between .NET forms and ABL windows, both the forms and windows in these mixed form and window families conform to the ABL window family mechanism (which allows the children to appear behind the parent) instead of conforming to the .NET form family mechanism (which forces the children to appear in front of the parent).