I don't think you can guarantee that no other events occur (and are
intercepted by the system or other apps).
I believe the following sequence is possible:
--WaltApp learns that long computation is needed.
--WaltApp calls FrmInitForm
--datebook appointment alarm is triggered, system switches to datebook
(WaltApp never receives frmOpenForm event for long computation)
I think what I would do in response to the trigger for the long
computation is to "unhide" a "please wait" message that's already on
the parent form, possibly hide some UI elements on the parent form,
do the computation, and then restore the UI. That way the system
event loop never gets a crack at things until you're done.
Hal
At 11:05 PM -0800 2/6/07, Walt Bilofsky wrote:
My app needs to put up a message while it is doing a possibly long
operation, within one event.
Is it possible to just call FrmInitForm and then FrmDrawForm to draw
the message, and then delete the form when I'm done? Or will that
have side effects?
--
For information on using the PalmSource Developer Forums, or to
unsubscribe, please see http://www.palmos.com/dev/support/forums/
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
