My app is running - some other app interrupts it - could be an alarm or a system dialog...
Before OS 3.5, I got a winExitEvent so I knew I was interrupted - and I just waited for a winEnterEvent to continue.
Then, in OS 3.5-4.2, I didn't get the winExitEvent until AFTER the interrupting app FINISHED. But this was still not an real issue, because my 68K app was truly interrupted and so it couldn't do anything until control returned to it - it then got both the winExitEvent and winEnterEvent and continued on its way.
BUT NOW - in OS 5.x, not only don't I get the winExitEvent in time, but also my application isn't blocked from running after it's interrupted. The result is that my application keeps running AFTER the external dialog appears, drawing over top of the dialog completely before losing all pen input.
Since most other applications seem to "just work" when being interrupted, what could I be doing wrong?
When my app gets "interrupted", all hell breaks loose, and this was never an issue before. But this is now a significant compatibility problem, and it can be quite dangerous when, for example, the user can't see a low batery warning.
Any advice is greatly appreciated! - Jeff
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
