Let me add 2 different cents on this thread:
1) There are times when you don't want the user to be able to cancel, or
even if you do, it's highly desirable to show the user that something is
happening (because otherwise they may THINK the unit is frozen even
though it isn't). We have used a "spinning beachball" in a couple of our
apps and users seem to like it just fine. Some people seem to have the
idea that the Palm "shouldn't" do that, and certainly for every day
operations like shifting from address book to date book or looking up
someone in the address book, it shouldn't, but all applications are not
the same, and sometimes this is simply the desirable paradigm.
2) One of the potentially long operations is DmQuickSort, which because
it is all happening in a single API call, is neither interruptable (can't
use a Cancel button on screen) nor do I have access to spin a beach ball.
Has anyone else dealt with this issue and figured out how to work around
it (short of bloating your code by implementing your own sort routine)?
Steve Patt
President, Stevens Creek Software
http://www.stevenscreek.com/pilot
The home of...
PalmPrint && UnDupe && AreaCoder && Handy Randy
Athlete's Calculator && PocketTimer && SnailMailer
Athlete's Diary && On Hand && Take An Order! && many more
