[progress Communities] [progress Openedge Abl] Forum Post: Re: Mixed Abl Window And Gui For...

Status
Not open for further replies.
M

Mike Fechner

Guest
Why do you need to know this? Do you need to be able to call back into your parent? Or do you need to "Parent" .NET Forms to ABL windows and vice versa. IMHO the actual parenting (Owner property of .NET forms) is not behaving as most users expect as it's causing child windows to be minimized when the parent (owner) is minimized. If you just need a handle/reference of your caller, I suggest you provide two additional constructors for your .NET Form: One with a HANDLE as the Parameter and another one with a System.Windows.Forms.Form as the reference. This way the caller (procedure that created the ABL window or an ABL GUI for .NET Form) can introduce themselves to the called form. oForm = NEW YourChildForm (THIS-PROCEDURE) or oForm = NEW YourChildForm (THIS-OBJECT) In case the Child is an ABL Window procedure, do a similar thing, with two input parameters: DEFINE INPUT PARAMETER phProcedureParent AS HANDLE NO-UNDO . DEFINE INPUT PARAMETER poObjectParent AS System.Windows.Forms.Form NO-UNDO . and then RUN yourchildwindow.w (THIS-PROCEDURE, ?) . or RUN yourchildwindow.w (?, THIS-OBJECT) .

Continue reading...
 
Status
Not open for further replies.
Top