No, nothing does. Here's my current pilotMain:
UInt32 PilotMain(TCUnShort cmd, MemPtr cmdPBP, TCUnShort launchFlags)
{
Err error = RomVersionCompatible (ourMinVersion, launchFlags);
if (error)
return error;
if (cmd == sysAppLaunchCmdNormalLaunch)
error = DoMainLoop();
return error;
}
very straightforward. RomVersionCompabile was generated by an older CW app
wizard.
Remi.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ben Combee
Sent: April 10, 2007 10:15 AM
To: Palm Developer Forum
Subject: Re: Fatal Exception during program installation, fine afterwards
> I'm only responding to:
>
> sysAppLaunchCmdNormalLaunch
>
> But then, that's all this application has ever responded to, and this has
> never happened before...
>
> Do I *need* to handle other launch codes?
No, but you need to make sure you don't use any global variable in
code that runs before you've determined that
sysAppLaunchCmdNormalLaunch is your launch code.
--
For information on using the ACCESS Developer Forums, or to unsubscribe,
please see http://www.access-company.com/developers/forums/
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
