You probably shouldn't use FrmPopupForm and FrmDoDialog together, it's not how they're intended to be used. FrmPopupForm returns immediately, and the expectation is that your normal event loop will run and dispatch the events, etc. If you want to use FrmDoDialog to present a form and not return until the form is dismissed, then I recommend looking at the sample code from the SDK Examples (the built in apps). There are tons of examples there of how to do this.
"Richard Coutts" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > maybe you should use FrmPopupForm instead of FrmDoDialog? > > I'm sure you're right, but am running into some Newbee issues using > FrmPopupForm. I know I'm missing something fundamental. My understanding > of FrmPopupForm is that it queues a frmOpenEvent and a frmLoadEvent. Up > until now, I've been using both FrmPopupForm and FrmDoDialog together -- > FrmPopupForm to queue the aforementioned events and FrmDoDialog as an event > loop that sends events to my registered handler. E.g., > > FrmPopupForm( formID ); > FrmDoDialog( formP ); > > Execution passes through FrmPopupForm and FrmDoDialog processes the events > FrmPopupForm put on the queue. If I only use FrmPopupForm, and lose the > call to FrmDoDialog, then my handler doesn't receive any events. > > Should I write my own event loop to replace my call to FrmDoDialog? I > doesn't sound as though that's what you're suggesting. I'm a bit confused. > > Thanks, > Rich > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
