Kirk,
Yes, this is a good idea, and the schema when there is central UI process
(worker) displaying a toolbar, and all other windows are created with
DIALOG(;*) by clicks on toolbar buttons / menu items is interesting, but in
this particular case not doable, as I work with existing application
Hi Peter,
When you call DIALOG(*) the dialog opens in the current process. But as you
saw execution continues on. The solution is to make a DIALOG call by itself
first and open the subsequent windows from there.
The suggestions I've heard are to think about having a single UI process.
This
peter,
depending on what type of progress you need to display..
Progress Component - part of 4D now - will display either a barber pole
(indeterminate duration) with text above and below, or a progress
thermometer (defined interation count), again with text above and below.
- Both of these run
"If the current process terminates, the forms created in this way are
automatically closed".
I have always had a DIALOG() window to keep the process from terminating, and
called the DIALOG(*) windows from within it. However, you may be able to start
a process with CALL WORKER, which does not
Hello Peter,
This is a good question. The actual behavior you are encountering is because
the process will die after the execution of the code.
Thanks to the worker it is now possible to use a worker to display dialog with
the * parameter. A worker never die until you kill it with KILL WORKER.
I maybe already asked this question, but anyway I am still a bit confused:
I wanted to use DIALOG with * as an additional parameter, but have problem
to make it work. I have app that display several info windows - like
palettes, progress messages, communication statuses etc.Currently, I often
6 matches
Mail list logo
