One example is an app that dynamically allocates and initializes a structure for data that would otherwise be in global variables - the pointer to the memory can be stored in a feature so that the app doesn't have to have any global variables. Very useful if you need to be able to access global information during non-normal launch codes and don't want your code to depend upon the availability of global variables. An example is an app with a database abstraction layer for opening/closing/reading/writing databases that can be used during system "Find" and beam receive when the app isn't running.
Mark Peters "Jay Bloodworth" <[EMAIL PROTECTED]> wrote in message news:74094@palm-dev-forum... > > On Sun, 2002-01-20 at 20:46, Ben Combee wrote: > > Features: good for small amounts of non-permanent data (all features are > > erased on system reset) and flags. > > > > Preferences: better holding spot for small amounts of data that you want > > kept around after a reset. Unsaved prefs should hold working data, > > while saved prefs would be user-controlled things that would need to be > > restored if the user erased his device. > > > > Ok. Can someone give me an example of an application where storing data > in feature memory would be preferable to storing it in unsaved > preferences? > > Jay > > > > --- > > This server is using the evaluation version of the Newsgroups > Interface, making messages limited to 1000 characters. This limitation > can be removed by upgrading to MultiView. > See http://www.lyris.com/ for upgrade information. > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
