At 9:00 PM -0700 1999/05/20, Richard Bram wrote: >Well, I don't want to deal with any user-generated events. They either >have to wait for the slowprocess to finish, or else cancel it. But >are you saying there are device events I better not throw away? >(hmm, like maybe low battery warnings, etc.) You got it. The OS allows the app first crack at ALL events, but if the event is not intended for the app, it MUST pass the event on to the OS. If the app is not ready for the event, it MUST leave it in the queue for later processing. Throwing away events the app isn't yet ready to process or just doesn't feel like processing will result in a kind of 'vitamin deficiency' behavior (to be anthropomorphic). Regards, Jim Schram 3Com/Palm Computing Partner Engineering
- Checking for user input when busy? Paul Gargan
- Re: Checking for user input when bus... Creative Digital Publishing Inc.
- Re: Checking for user input when bus... Richard Bram
- Re: Checking for user input when bus... Jim Schram
- Re: Checking for user input when bus... Ronald H. Nicholson Jr.
- Re: Checking for user input when bus... Bob Ebert
- Re: Checking for user input when bus... Richard Bram
- Re: Checking for user input when bus... Jim Schram
- Re: Checking for user input when bus... Steve Patt
- Re: Checking for user input when bus... Neil Rhodes
- Re: Checking for user input when bus... Bob Ebert
- Re: Checking for user input when bus... Steve Patt
- Re: Checking for user input when bus... Chris Faherty
- Re: Checking for user input when bus... Greg Winton
- Re: Checking for user input when bus... David Fedor
- Re: Checking for user input when bus... Bob Ebert
