On Sat, 6 Mar 2004, Ben Combee wrote: > 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.
That's what I feared. I could probably use feature memory instead to pass stuff back. > 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. It would make more sense to have it over there if I were working on ARM-native versions of my apps. That's not the case... right now, I'm just trying to get my m68k apps working as they were before through PACE. If taking stuff over there better facilitates bringing questions about bugs and/or changes to their eyes, then sure. -- ----------------------------------------------------------------------- Brian Smith // avalon73 at caerleon dot us // http://www.caerleon.us/ Software Developer // Gamer // Webmaster // System Administrator "With enough soap, you can blow up just about anything." -- Tyler Durden (Brad Pitt), Fight Club -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
