Simply don't broadcast any user defined code. It'll end in tears!
The PalmOS 3.5 Notification Manager is a better mechanism. It'll be even better when
we can register notification ids as we can
with creator ids.
-C
Danko Radic wrote:
> (PalmOS 3.0)
>
> Let's suppose I have 2 applications: Receiver (that receives messages via
> PagerCard or something else) and Viewer (used to view result dependent on
> received message). When Viewer is active application and new message
> arrives, Receiver is trigged by special action code, receives message,
> refreshes DB and sends MY CUSTOM action code to Viewer to notify that.
> My custom action code is defined 'by the book' as
> sysAppLaunchCmdCustomBase.
> Receiver sends it via
> SysBroadcastActionCode()
> API call and Viewer handles it well.
>
> Now, since sysAppLaunchCmdCustomBase is only some *number* in fact and
> SysBroadcastActionCode() sends it to *ALL* UI applications, what
> would happen if there is some other application on same Palm that has
> defined that same *number* as action code and sends it or responds to it?
> CmdPBP is definitely wrong in such situation and it may cause app to
> crash.
>
> How to handle such situations (risk of overlap custom launch codes for
> different apps) in general?
>
> Rgds,
>
> -DR
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palm.com/devzone/mailinglists.html
--
Christopher Hunt
Class Action Pty. Ltd.
Complete time zone management for the Palm(tm) connected organizer.
Check out http://www.classactionpl.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
