Logan Shaw wrote:
Just a guess, but what may be going on is this: when Palm OS wants to launch an app on the card, it first copies the PRC to the internal RAM. Then, it launches it. Then, when the app exits, it erases the copy that's in the internal RAM.
Logan, it seems this is exactly what happened.
In that case, the app never gets deleted from the storage heap. And then, NEXT time you launch the app from the SD Card, what does the OS do? It goes "hey, this is already IN memory, there is no need to waste time copying it", and it just launches the in-memory version and remembers not to delete it after the app exits. Presto, you have a "stuck" version of the app in the storage heap.
You were right! I checked the storage heap with FileZ and behold, there was my app, even with the SD card ejected. I deleted it, and now my app is being updated correctly. Thanks for your diagnosis!
Personally, I find it's much more convenient just to hotsync the app onto the device every time I want to test. I often hit the hotsync button as I start building to make sure all the other crud is hotsynced. Then when the PRC is built, I hotsync again, and it doesn't take long to install the app because the app is the only thing that has changed since the last hotsync.
When developing my app the first time I had to test IrDA functionality, and I used Pilot Install to do a quick hotsync of just the test app. Unfortunately, they have not updated their program to the new version of HotSync that the T5 uses.
Thank you for your help! Mark Cushman http://cushman.net/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
