I tried the approach of watching the characters, and it was indeed a pain to maintain. The worst cases are the characters that sometimes bring up dialogs and sometimes don't. I recall two such characters. One is a low battery character that only sometimes presents a low battery dialog. Another is an attention manager character that only sometimes brings up the attention manager dialog.
I agree that the winEnter and winExit event problem is indeed a flaw, and a fairly serious one. Somehow I don't think it's very easy to fix. If you can't rely on getting an event to notify you of something, you really can't do much with the event, and the whole thing has very little value. More than anything, it tempts you down a dead-end. One strategy I've tried is to read the tick clock before sending any event to SysHandleEvent, and then to check how much time has passed. If it's been too long, assume a dialog has been presented, and retroactively pause everything as of the time when the event was sent to SysHandleEvent. I can't say this strategy worked, but I think it can be made to work ;-) Sadly, there are no easy answers here. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
