At 9:21 AM -0800 12/10/99, Richard Hartman wrote:
>Do apps get some sort of cleanup opportunity
>when they are deleted, perhaps an app start
>w/ a special start code?
Nope. You could allocate a chunk in the dynamic heap with owner ID 0 and put your trap
code in it. That should prevent a crash on app deletion. If your trap isn't called too
often, you could have your trap handler check for the existence of the app and disable
(and delete?) itself. But all this is just a hack - literally! Why not use HackMaster
or some other system for dealing with trap patching?
I suppose HackMaster doesn't really solve the problem since users can delete hacks
before disabling them. Maybe hacks should be given the same creator ID as HackMaster
so they couldn't be deleted from the launcher. Then HackMaster could have a Delete
command for hacks. This still doesn't address the issue of deleting HackMaster itself
(along with all the hacks).
It looks like a delete notification is indeed required. But how do we delete apps that
crash on delete notification? Up-arrow again? Yuck!
Thinking out loud...
-
Danny Epstein, Applied Thought Corporation
Have friends with Palm organizers? Get BeamBooks!
http://www.appliedthought.com/beambooks
