With versions up through 5.x, I can pass arguments via a parameter block to an app I call with SysAppLaunch, but can also pass return values back to the calling app through that same block of memory. With Cobalt, that doesn't work so well... with the exact same code, the returned values come back seriously corrupted. Is this a bug, or just something else that's changed? If it matters, it's double values that I'm passing back through the parameter block.
This is a change. The parameter block is actually copied into the new process that gets created on a sublaunch -- the sublaunched app can't affect the data in the original app's process.
Of course, a reading of the SysAppLaunch docs in the Cobalt SDK says that "SysAppLaunch" is discouraged now; you should use SysAppLaunchLocal or SysAppLaunchRemote instead.
I'd agree -- there needs to be a better description of what SysAppLaunch really does on Cobalt; the current docs still refer to the resource chain, a concept not used for native apps.
BTW, this discussion would probably be better on the protein-forum mailing list. I know several of the Cobalt engineers read that list pretty closely.
-- Ben Combee, senior DTS engineer, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
