Does your app treat sysAppLaunchCmdSyncNotify as an exception case, and
assume that if the code is not sysAppLaunchCmdSyncNotify that everything is
ok ... or does it require that the launch code be
sysAppLaunchCmdNormalLaunch in order to proceed and treat all other codes as
reasons to exit?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Roger Moore wrote in message <11722@palm-dev-forum>...
>
>Okay thanks everyone! I can now download the app. I put in a line that
exists PilotMain immediately if I get a sysAppLaunchCmdSyncNotify. I do
have to do a soft reset after I see a message that instructs me to "reset
your Palm III by tapping the button below". When I do that I get the
"Welcome to Palm III" screen but I still have to do a manual
>soft reset to continue. My app is loaded however :). Is having to do the
soft reset normal and if not how can I get rid of it?
>
>Peter Epstein wrote:
>
>> When your app is installed via HotSync, it should get a sync notify
launch code. I don't think you'll get that when you install the app using
the debugger. You don't have access to globals when handling that launch
code, so it's pretty easy to make a mistake in the handling of that launch
code. This might not be the problem, but it's worth a look.
>> --
>> Peter Epstein
>> Palm Inc. Developer
>>
>> --
>> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
