>To summarize - indications of activity and possibilities of cancellation >are HIGHLY desirable for operations that can take 30 seconds. (catching up on the threads here; I was away...) Have you considered the progress manager? It doesn't solve the DmQuickSort issue but does handle many progress-display situations. An alternative method: if any of the *EventAvail() functions say there's an event, perhaps you should use that as a signal to exit out to the main event loop and continue the slow operation when you next get a nilEvent. -David Fedor Palm Developer Support
- Re: Checking for user input when busy? Ronald H. Nicholson Jr.
- Re: Checking for user input when busy? Bob Ebert
- Re: Checking for user input when busy? Richard Bram
- Re: Checking for user input when busy? Jim Schram
- Re: Checking for user input when busy? Steve Patt
- Re: Checking for user input when busy? Neil Rhodes
- Re: Checking for user input when busy? Bob Ebert
- Re: Checking for user input when busy? Steve Patt
- Re: Checking for user input when busy? Chris Faherty
- Re: Checking for user input when busy? Greg Winton
- Re: Checking for user input when busy? David Fedor
- Re: Checking for user input when busy? Bob Ebert
