My application is a frame based app (a game). So it peeks for any messages in its queue with a time out. Then if there are none, it goes and does a frame and comes back. So it relies entirely on getting messages to know when it's been interrupted.
As mentioned, in pre-OS 5, even when it got interrupt messages late, it didn't seem to matter because the program itself stopped running during the interruption. Now I get problems of interrupting programs running simultaneously, or not at all. I generally try to pass on any signal I don't understand to the system, but even the most rudimentary interrupts don't seem to work now. For example, when an Alarm goes off and puts up a dialog, what events are your app supposed to get? As far as I could tell, winExit was the only option, and since OS 3.5, you get that too late... Obviously, this is a minor issue with people whose apps are purely event driven, but I'm sure there's a lot of game programmers out there - and helpful tips? Much Appreciated. :) - Jeff --- In [EMAIL PROTECTED], James <[EMAIL PROTECTED]> wrote: > In OS 5.x, exactly how does your application continue to run? > > Your application normally can't receive additional events, because even in OS > 5.x, AFAIK there's a single, shared event queue, and if there's a dialog > active, that dialog's event handler grabs all events. > > Do you mean that your application continues to receive notifications? If so, > then that's the same behavior as in previous OS versions, and you need to check > to see if the active form/window is yours within your notification handlers. > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
