Hi Danny, and thanks for your answer. On Tuesday 16 April 2002 19:31, Danny Epstein wrote:
>> The application only "answer" to sysAppLaunchCmdNormalLaunch. > > Visually trace through your code, starting at the top of your PilotMain, > and see what it does when it gets the sysAppLaunchCmdSyncNotify launch > code. Check for accesses to global variables; these aren't allowed. (I've > made the mistake of storing the OS version in a global.) If you don't see > anything, try writing a little test app that uses SysAppLaunch to send your > "real" app a sysAppLaunchCmdSyncNotify launch code. If you're using > CodeWarrior 8, you can do this without writing a test app. I can't debug, as the problem occur only on a customer device, but I have checked the source code ( one more time ) and PilotMain does only take in account sysAppLaunchCmdNormalLaunch and return 0 in other cases. This PilotMain function is exactly the same as in tons of other applications, so I'm almost sure there is no problem at this level. By the way, only 3 customers have reported a similar problem, and at least 2000 other does not have a problem at all, so I guess the trouble is on the customer device ( or with their Palm desktop program ), but I don't have any idea what can be the reason of the problem, as they say they have enough free memory on the device and they have successfully installed an application which is as big ( which mean their available memory is not "fragmented" ). This application only run on colors Clie devices, having Palm OS 4.0 or 4.1 Any other idea ? -- Daniel Morais -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
