Thanks for the info, but I am still at a loss. There is no application in
this scenario which 'should' be receiving the sysAppLaunchCmdSyncNotify
notification. I have done some tracing, and the plugin DB is being sent a
launch code (not sure which) after it is accepted on the target device. The
problem is, my plugins presently don't have a PilotMain as such, and expect
various parameters in the 'entry function', which the Launcher seems to be
calling (obviously without the required parameters)
Suppressing this sending of the notification is what I need to achieve,
somehow. I tried changing the 'filename' of the plugin to have a .PDB
extension, but that didn't work; the notification is still sent.
The only thing I can think of, is that the launcher code must do a scan of
the received DB, see that it has a CODE resource, and try to send it the
notification.
Any ideas how I can get around this?
thanks,
SP.
>Subject: Re: Fatal when beaming
>From: "Danny Epstein" <[EMAIL PROTECTED]>
>Date: Fri, 3 Nov 2000 18:04:11 -0800
>X-Message-Number: 69
>
>"Lab" <[EMAIL PROTECTED]> wrote in message news:29103@palm-dev-forum...
> > Is there some launch code that they are sent on the other Palm? ie. does
>it assume the resource DB is an app or something crazy like that?
>
>Just looked at the 3.5 source for Launcher. Sure enough, it sends
>sysAppLaunchCmdSyncNotify to the received database unless it's a PQA.
>Definitely not right.
>
>The latest source sends this launch code to:
>- the received database, if it's an application (type == 'appl')
>- to the application with the same creator ID, otherwise
>If the received database isn't an application, and there is no application
>with the same creator ID, no sync notify launch is done.
>
>The work-around is to send the plug-in database to your application, rather
>than to Launcher. I assume you're using the extension ".prc", and that's why
>Launcher's getting it. You could invent a new extension or MIME type, or you
>could specify the target creator ID. For a Palm-specific app, the latter is
>fine. Another work-around would be to make your plug-ins handle sync notify.
>Weird, I know, but it should work.
>--
>Danny Epstein
>OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
