What I've done in the past is 1) close all forms and prepare to exit (no more event servicing), 2) clone a minimum copy of myself, 3) register the clone and send it a notification, and 4) exit. The clone receives the notification and 1) marks itself as recycleable, 2) does whatever work is needed, and 3) exits, and is eventually deleted.
Alternatively, 1) copy the relevant code to feature memory or heap, 2) set a proc alarm to that memory, and 3) exit the app. When the alarm fires, 1) the code image is called and does it's work, 2) the image removes itself just before returning from the alarm callback, 3) returns. Other alternatives as you see fit. On 2/15/07, Lionscribe <[EMAIL PROTECTED]> wrote: > > The right way to do it is to have the extra resources in a seperate > database, which the user should install if needed, though it get's > complicated if user runs program from card. > LionScribe > > -- > For information on using the PalmSource Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- yisdersomenimororsisasisdenderisorsis? Jeff Loucks -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
