open a Windows from a Dialog

[grunnpi]

Hello Everybody,


We are using both Dialog and Windows to design screen, and want to open
a Windows from a Dialog button call.

As Dialog cannot open Windows (WAIT-FOR issue), was wondering is it
would be possible to change Windows behaviour by code.
Meaning, using a parameter + inside code to handle : "Windows mode" /
"Dialog mode".

Please note for various excuses, we cannot afford to fully redesign one
screen from Windows to Dialog nor Dialog to Windows.


My guess was :
- inside 4GL code ? (but maybe AppBuilder won't appreciate)
- using .dll code ?

Config :
- OE 10.1b sp2
- Windows 2K / 2003 server


Hope someone can have a clue.

Cheers,

Grunnpi

 

[RealHeavyDude]

You need to run the window persistently in order to avoid a second WAIT-FOR in the session. If you look into the main block of any window you will find something like

IF NOT THIS-PROCEDUREERSISTENT THEN WAIT-FOR CLOSE OF THIS-PROCEDURE

for that reason.

Heavy Regards, RealHeavyDude.

 

[grunnpi]

really ?!
I've seen this automaticly generated line hundreds time...

Let's try it asap.

Heavy thank you Dude !

 

[grunnpi]

But I've tried running as persistent today.
Didn't trigger error message anymore, but as disabling WAIT-FOR, windows open and close immediatly. Not so usefull.

After some test & try, we figure out that coding like this :

HIDE FRAME myDialogFrame.
RUN myWindow.w.
DISPLAY FRAME myDialogFrame.

It's do the job.
So easy.

Thanks for supporting, see you next time !

 

[RealHeavyDude]

The way persistent procedures work is that the main block gets processed and then the procedure stays in memory until you explicitly close it. Is is possible that you have some code in the main block after the wait-for that does something like that?

Heavy Regards, RealHeavyDude.