I still think that 4 init/cleanup phases should be defined:
installation / deletion
activation / deactivation
I do not have specific examples of the usefullness of
any specific phase ... but generalization doesn't hurt
and just because I can't think of a use doesn't mean
somebody else can't.
I -do- seem to recall that there have been hacks that
could have made use of a "call-before-deleting" routine,
but it's been a while so I don't recall which ones. I suppose
I could check the archives ...
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Aaron Ardiri wrote in message <38273@palm-dev-forum>...
>
>> Here's a first rough idea for a compatible solution:
>
> <snip>
>
> why not get the developer to write a routine that accepts one
> boolean parameter? false = startup, true = shutdown
>
> that way, they just define one code resource, one function to
> do all the cleaning up of the trap resources (if there are any)
> provide the function spec they should implement, and put it in
> a specific resource:
>
> code9999.bin <-- x-master memory management
>
> then, x-master can check for that resource, if it exists,
> load and execute.. otherwise.. no memory management required.
>
> how compatible will a hack be with hackmaster if you actually
> add a trap for id 999? doing something specific is really the
> way to go here, you dont know exactly how the other programs
> work, and, if they will fail using the technique you explained.
>
> with this system, only x-master looks for code9999.bin :)
>
>// az
>[EMAIL PROTECTED]
>http://www.ardiri.com/ <--- free games!
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
