Thinking it over there are many events that could interrupt the player, not necessarily related to an incoming call (for instance inserting a card in the slot). I tried to set up a counter so that my app needs to receive AppStopEvent many times before it exits, and it works as expected! That allows to keep on playing chess after receiving a call - my wife has a special intuition for calling me on those moments.
Of course the official new release (1.1) of Palm Chess Client will feature something more sophisticated. I'm thinking of displaying a dialog form when AppStopEvent is received, of the kind "Do you really want to quit Chess Client? (Quit) (Keep playing)". If no action is taken the form will disappear within 3 secs canceling the stop request. If another AppStopEvent is received while the form is displayed the app will quit. The user will be able to customize the app by enabling this behaviour always, never, or only when playing a game (the default). Thank you both for the help. > Thanks David for cutting through my clutter of events and > such and given the actual simple answer to Joker's question - > namely, if you don't want ot exit your app, then ignore the > AppStopEvent. > But, as Joker says, if he ever wants to exit his app he'll need > to know which AppStopEvent to ignore. So, returns the clutter of > events and such. > I suspect you could watch the various phone events and > notifications. If you see one that implies a switch to the phone > app, you could for one time ignore the imminent AppStopEvent. > Or, ignore all AppStopEvents until an app exit button is > pressed, but who wants an exit button in a Palm app :) -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
