Regis St-Gelais wrote: > Simulator and emulator (specialy with debug roms) are often > generating more FrmUpdate events to simulate low memory > situations. > Your forms should always be prepared to recive a FrmUpdate event > at any time.
And return true to them in modal dialog handlers to avoid a cascade? Luc Le Blanc http://www.speleo.qc.ca/Auriga > "Luc Le Blanc" <llebl...@cam.org> a écrit dans le message de > news: 187...@palm-dev-forum... >>I display a map in non-modal form that can launch a modal dialog >>upon a menuEvent. When the help form is closed in the modal >>dialog, the modal dialog receives a frmUpdateEvent, that gets >>ignored (nothing to do.) A frmUpdateEvent is then received by >>the "parent" (non-modal) form, that uses this event to redraw >>the map. Everything looks fine on a real device, but on a >>Simulator, the >>map "behind" overwrites the overlapping dialog >>that is still open. Is the Simulator telling me something's >>wrong in my code, or should I ignore this as a Simulator >>misbehavior? >> >> >> Luc Le Blanc -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
