"Gary Spinelli" <[EMAIL PROTECTED]> wrote in message
news:43702@palm-dev-forum...
> I'm attempting to trap the sysAppLaunchCmdCardLaunch code from my
PilotStart
> routine and force my application to exit immediately. I'm catching the
code
> OK , but when I try to exit the application by returning from PilotStart
> with a non-zero error, it appears it is getting launched again with a
launch
> code of zero. What am I missing and is this the correct way to prevent my
> application from being launched from the expansion card?
I'm not sure why you'd want to do this, but you've got the logic backwards.
If you don't want Launcher to do a normal launch on your app, you want to
handle the card launch and return "success". There is an err field in the
command parameter block for the card launch. Set this to zero (or anything
other than expErrUnsupportedOperation) and it'll prevent the subsequent
normal launch from happening.
The command parameter block for the card launch includes all the info you
need to access other files stored with your app on the card. But when an app
is launched from a card, it's still copied into main memory (and
automatically deleted later). So I'm not sure why you'd want to prevent a
card launch - it should work fine.
--
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/
