I thought I could "pass through" the update to the underlying form by doing this:case frmUpdateEvent: switch(event->data.frmUpdate.updateCode) { case 40: FrmUpdateForm(underlying_form_id, 40); handled = true; break; } break; in the popup form's handler. But, this results in an infinite loop of updates to the popup form. (Why is that?)
FrmUpdateForm doesn't really post the update directly to the form. It actually just posts a frmUpdateEvent. Your popup form then gets the event again. Part of the solution is to make sure your frmUpdateEvent handlers only process the update event when the form in the event structure matches itself. However, this still leaves you with the problem of how to update the lower form. I just tried out this scenario with MemoPad on the NX70V. If you have the details dialog up, the memo pad will delay changing until you dismiss that dialog. Perhaps the app just sets a flag and the forms check that when the become active and resize then.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
