1. openDialog()
Hello to Derek and all Friends,
« .. the openDialog() routine opens a modal window then waits for that window
to close before executing the line after the openDialog() statement.
During this time, any event handlers set up for the dialog window would still
fire correctly. »
Needing to use this feature, I tried the sample as into the win32Lib-59-1 Doc:
include win32lib.ew
sequence filename
filename = ""
constant
myFileDialog = create( Window, "", 0, Default, Default, 400, 400, 0 )
,Xt = create( PushButton, "Exit", myFileDialog, 306, 5, 36, 20, 0)
,RE = create( RichEdit, "", myFileDialog, 0,0,0,0, 0)
while length(filename) = 0 do
openDialog( myFileDialog)
end while
I had to shut down the computer to exit some hundreds
of opening-autoclosing windows! (OS Win2000 server)
could you explain how to obtain an openDialog() that waits
to be closed before the program process the next step?
thanks, thanks..
Antonio Alessi
2. Re: openDialog()
Antonio Alessi wrote:
>
> Hello to Derek and all Friends,
>
> « .. the openDialog() routine opens a modal window then waits for that window
Hi Antonio,
this is how I thought it did work. I'm travelling this week so I'm not at my
normal computers and can't play with the function yet.
Can anyone else help until I get back home?
--
Derek Parnell
Melbourne, Australia
Skype name: derek.j.parnell
3. Re: openDialog()
Hi Derek,
thanks for your care.
As an answer to myself, but dedicated to others :)
the openDialog() procedure cannot behave as in the example of the win32Lib;
if called by an independent command it immediately closes: it needs to be
called by a routine started from a setHandler() to be correctly activated.
However this gave me a better idea in building a tool that can help the
advanced developers (or who is managing too much complex sequences) in
their debugging; it deals with the « dEbUg_Magic_Box ».
This tool is based on the double use of the openDialog(), in order to
[pretty]watch without difficulty [and interact with] sequenced variables
of any lenght and depth, even inside a loop and/or without interfere with
the running program.
It will be available in hours as the best contribution of mine to the RDS.
Just the time to write the help now..
Antonio Alessi
4. Re: openDialog()
Antonio Alessi wrote:
>
> Hi Derek,
>
>
> thanks for your care.
>
> As an answer to myself, but dedicated to others :)
> the openDialog() procedure cannot behave as in the example of the win32Lib;
>
> if called by an independent command it immediately closes: it needs to be
> called by a routine started from a setHandler() to be correctly activated.
>
> However this gave me a better idea in building a tool that can help the
> advanced developers (or who is managing too much complex sequences) in
> their debugging; it deals with the « dEbUg_Magic_Box ».
>
> This tool is based on the double use of the openDialog(), in order to
> [pretty]watch without difficulty [and interact with] sequenced variables
> of any lenght and depth, even inside a loop and/or without interfere with
> the running program.
>
> It will be available in hours as the best contribution of mine to the RDS.
> Just the time to write the help now..
>
> Antonio Alessi
Hi there,
Are you talking about opening a dialog and then making sure
another dialog cant open up without the first one closing
first?
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with fighting the good fight,
but i can not live without fighting it".
5. Re: openDialog()
- Posted by Antonio Alessi <a.admin at myway.it>
Mar 16, 2006
-
Last edited Mar 17, 2006
HI Al,
how are you?
Something like, but not exactly: talking about opening a dialog that
must be closed before any following program step can be executed.
However the best answer to that is given now by this new tool:
http://www.myway.it/EU/dEbUg_magic_box.zip
ciao,
antonio
} when you understand Euphoria, it's like to fly! }
