Oho a religious war in the offing ;).
Well you can probably tell how I felt about the feature...I never really
liked it because it didn't seem to fit with the appStopEvent model...why
was there never an appPausedEvent (or appBackgroundedEvent)?
You have to resort to kludges like looking for keyDown events of a
certain flavour. It also meant (depending on your app) you had to keep
track of your background/foreground state as many apps have to do
special things when they come to the fore (gray scale games under PalmOS
2.0 for example).
But then maybe we're talking from different perspectives (user vs
developer) and goodness knows it's a rare thing when users and
developers agree on feature functionality ;).
Stuart Nicholson
Programmer
Firepad Inc.
> ----------
> From: John Marshall
> Reply To: Palm Developer Forum
> Sent: Tuesday, July 18, 2000 2:33 PM
> To: Palm Developer Forum
> Subject: Re: appStopEvent and PalmOS 2.0
>
> Stuart Nicholson <[EMAIL PROTECTED]> wrote:
> > Fortunately Palm Computing removed this annoying feature (which has
> no
> > merit that I can see other than to confuse application developers)
> in
> > PalmOS 3.0 and higher.
>
> Oh please...
>
> It was a very useful feature. I used to use the applications screen
> as a
> clock all the time: one tap to see the time, one tap to go back to
> exactly
> where you were. Very fast -- no application startup or display
> updates.
>
> I miss that feature. :-(
>
> Ob-dev-list: If that was a confusion for developers, it's only
> because
> they were assuming more control than they really needed.
>
> John
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
> please see http://www.palmos.com/dev/tech/support/forums/
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
