Hi,
Am Mi, den 30.06.2004 schrieb Danielle O'Hallisey um 21:05:
> I have been looking for awhile now to find a way to launch my app following
> a sync, without user interaction. It occurs to me that
> sysAppLaunchCmdSyncNotify creates an opportunity to interact with the app
> following a sync, so long as I make the conduit bi-directional and send a
> change from the host PC to the Palm device (the idea being to get data back
> to the PC mainly, but this seems like a mechanism to get back to my app).
Depending on your planned device compatibility, you may want to check
out the notification manager, more specifically sysNotifySyncFinishEvent
- this way you do not need to send data back, but it will not be as
backwards compatible.
> So, when I hack the standard Address application to include the standard
> startup code under the case sysAppLaunchCmdSyncNotify: definition, does this
> explain why the program will compile and load into my Tungsten E, but fails
> to properly start, both when I sync following changes to the Address book in
> Palm Desktop, and when I tap the icon in the main user interface?
When you tap the icon in the launcher, it should start as globals etc
are available in this case.
> case sysAppLaunchCmdSyncNotify:
> {PrvAppHandleSync();
> error = PrvAppStart ();
> if (error)
> return (error);
> FrmGotoForm (ListView);
> PrvAppEventLoop ();
> PrvAppStop ();
> }
> #endif
> break;
This won't work, though. But you could just use
case sysAppLaunchCmdSyncNotify:
SysCurAppDatabase(&cardNo, &dbID);
SysUIAppSwitch(cardNo, dbID, sysAppLaunchCmdNormalLaunch, 0);
break;
--
Daniel Seifert <[EMAIL PROTECTED]>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
