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).
However, I note the following in the definition of Action Codes in the
SystemMgr.h file:
//Restrictions: No accessing of global or static variables; no User
Interface calls
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?
The code looks like this:
#ifndef SINGLE_SEGMENT_CHECK
case sysAppLaunchCmdSyncNotify:
{PrvAppHandleSync();
error = PrvAppStart ();
if (error)
return (error);
FrmGotoForm (ListView);
PrvAppEventLoop ();
PrvAppStop ();
}
#endif
break;
I can see the possibility that I will need to write an app from the ground
up to properly test this mechanism for my desired goals, but I guess what I
am wondering is whether the statement �no User Interface calls� means that
it is really not possible to launch an app from this point in the sync
process under any circumstances.
As always, any help at all would be appreciated. I have defined this
problem a number of different ways, but each seems to run into a snag
somewhere along the line�
Thank you,
Danielle O'Hallisey
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
