> okay, i think i see what you mean...you want a GUI that starts a loop
> which can conditionally spawn a second window, and when that second
> windows is closed, it returns to the loop and continues processing...
yes.
> i can't figure it out either...my current theory is that since the
> Loop_Click event has not exited, another click event (OK_Click) cannot
> be registered...
I would think this is a common problem. If somebody want to process
a file line by line looking for errors they would want to pop up a
window to display the error and then let the user continue on with
the processing.
> you can do something like this to exit the loop (thereby exiting the
> click event) prior to displaying the window, but then you have to pull
> some shysty manoeuvres to maintain state and get the loop going again:
Yeah, that becomes a pain to deal with each time.
I would think some kind of 'stop and wait' function would exist. You
can popup a message window, ie.
Win32::GUI::MessageBox(0,"Some message","Info",64);
..and that will wait for a button click in the middle of a loop so I would
think you could do this with a user-created window.
-david