David Fedor wrote:
> > * Why have Palm departed from broadcasting launch codes for
> > notifications?
>
> Because sending a launch code to every app installed takes a lot of time,
> if there are a lot of apps. With the notification manager, only the apps
> who care get notified. Much, much faster.
What's a long time, and what's much faster? Very subjective comments. I use launch
codes all the time and do not experience problematic delays. Additionally, given
the selective nature of the notification manager, you typically won't get many,
many apps getting notified via launch codes. Lastly, if SysAppLaunch needs
tweaking then tweak it.
I for one would prefer launch codes. See below for more reasons other than just
sticking to convention.
> > * Apart from callbacks being unconventional for notifications in OS's
> > < 3.5, how will one determine launch flags within the callback
> > i.e.. whether globals are available etc.?
>
> Good question. Best to assume you don't have globals; you nearly always won't.
If you don't assume globals and then re-open a database for rw access you will
cause an error if your app is already running, and has rw access. This is a common
problem.
You NEED to be able to determine globals.
Additionally by using globals you can assume a context that otherwise takes some
time to setup (opening databases etc.). Thus having launch codes that inform you
of new stacks, globals etc. can in fact save time!
Launch Codes rule! I think that the Notification Manager will be virtually useless
to me unless I can determine my environment. : -)
> > * Can we expect to see Palm provide a registry for custom notifyType
> > values just as they do for creator IDs?
>
> Just use the creator id registry for the notification codes.
Why not provide another one?
--
Christopher Hunt
Class Action Pty. Ltd.
Complete time zone management for the Palm(tm) connected organizer.
Check out http://www.classactionpl.com/
