So I thought if my app opened the .pdb file and stored the DmOpenRef in feature memory, then my callback function can simply look at it and use it to process the .pdb file that is already opened. That way, if another app gets launched, my callback will still run and can use the .pdb file.
My question is: do you think this will actually work ok?
Storing a DmOpenRef in a feature should work fine. However, the problem is that other applications can then run, doing anything, including wreaking havoc. I suspect there are any number of things an application could do to make that reference invalid.
Steve, by that, do you mean that they could cause havoc with my .pdb file if they know what it is I've written to the feature memory? Or that an application could just arbitrarily go in and smash my feature memory to pieces? Can applications therefore interrogate the layout of feature memory and see what it is that resides where?
Point I'm getting at is that I might have to make a trade between integrity and the convenience of having feature memory control my database reference?
Just thinking aloud here. If my app responds normally to a stop event but fails to unregister the callback and fails to close the DmOpenRef in feature memory, then the callback could in theory just keep ticking over every second? Is so, I can see a use for that in my app where GPS logging is concerned.
Thanks
Peter
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
