Every event you put into the event queue will come back out (unless your app
exits). The question is who gets the event back out. If you call
FrmCustomAlert, it's event loop will be the one to get the event. I don't
consider this a problem.
If you want to see every event go through your main event loop, don't call
routines that open dialogs and block until the dialog is closed. Such
routines must have their own event loops. If you need to see every event,
but not all in the same main event loop, then you can use some of these
routines, as long as you can pass it the address of a routine that'll see
every event processed by the dialog. For example, FrmDoDialog is okay since
you can specify the event handler for the dialog, and that handler gets
first crack at all events in the dialog's event loop.
Since the routines that have their own event loop are blocking, why can't
you just wait until the routine returns before posting the event to the
queue?
--
Peter Epstein
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
