Go back to what? If I use the launcher to fire up
another app, the one that was running when I opened the
launcher will receive the AppStopEvent and quit running.
(Just exactly when it receives this event depends upon
which launcher you're using.) If I put a Done button in
my app that causes it to just drop out (just like the
AppStopEvent would), that won't take me back to the app
that was running previously; it will likely return to
the app launcher. Which is okay, I suppose, but kinda
pointless. Why clutter up my app with a Done button when
there's already a button that does the job for me (the
one with the house or the word 'Applications' on it)?
--
Roger Chaplin <[EMAIL PROTECTED]>
> At 12:08 PM 10/26/99 -0400, you wrote:
> >HOWEVER, you shouldn't have a DONE button for your application.
> >That's not how the Palm 'user convention' works. On Palm, the user
> >expects to be in one application until (s)he chooses to be in
> >another. You app will 'shutdown' as a result of the user's starting a
> >NEW application. It shouldn't just 'shutdown' on its own EXCEPT in
> >the condition that you have an error initializing the app. In that
> >case, it's OK to 'exit' back to whatever was happening.
> >
>
> Don't you think it's OK to 'exit' back to whatever was happening before,
> even if you didn't get an error?
>
> Maybe it's up to the developer and his/her users. If they want a "DONE"
> button, fine - except the developer must realize that it doesn't really
> mean 'QUIT', it means "Go back to whatever the user was doing before".
>
> After all, you can launch one app from another app, and having a "quit"
> does let you go back to whatever launched the 2nd app.
>
> Don't you get annoyed at having to re-launch things just because you ran a
> calculator or something to get an interim value or to check on something?
>
>
>
>
