I had the same need, but could not find a proper way to spawn the calculator and return to my application afterwards. So instead, when the user hits the calculator button, I link my application to the calculator button before letting the OS handle the keyDown event, so that when the user is done with the calculator, hitting the calculator button again relaunches my applications, where I restore my previous context (stored in my application preferences), and reset the calculator button to its original setting (kept in my application preferences).
-- Luc Le Blanc [EMAIL PROTECTED] a écrit : > >... "Remember, if the second app returns to the OS without having >setup > a "follow-on" app, your original app will be relaunched ..." > > This is exactly my problem, the application (the calculator in my case) > is executing itself but when I'm done with it, my application does not relaunched > (return to launcher). > I'm using: > > err = DmGetNextDatabaseByTypeCreator( true, &stateInfo, 'appl', creatorID, > true, &card, &id ); > err = SysUIAppSwitch(card, id, 0, 0); > > >-- > >Ben Combee <[EMAIL PROTECTED]> > >CodeWarrior for Palm OS technical lead > >Palm OS programming help @ www.palmoswerks.com > > Thanks, > Gonzalo Piano. > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see > http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
