> 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.
There's no need in this instance to do a broadcast, since you know that
Viewer is the oly app that needs to be notified. Use SysAppLaunch instead.
> 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?
--
Neil Rhodes
Calliope Enterprises, Inc.
1328 Clock Avenue
Redlands, CA 92374
(909) 793-5995 [EMAIL PROTECTED] fax: (909) 793-2545
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
