From: "Vesselin Bontchev" <[EMAIL PROTECTED]> > And, of course, I'll have to figure out what to do under PalmOS > lower than 5.0. I guess, I'll have to write a hack (snip) > I don't want my application to depend on the presense of a > third-party hack manager... > Did that too. In fact, since the client decided that they didn't want Palm OS 4 support I'd be quite happy to sell you the implementation pre-written :-). I get the impression you're writing this yourself and so that probably isn't an option but if it is let me know.
You're correct about the hack - the basic theory is documented (partly) and from memory I worked from a test app (DemoHack) which uses HackMaster support. This provided a start while I worked out how to implement the hack without HackMaster. >From memory you create a code segment, attach it to your app as a resource (Ben's answer to my question on how to do this should be in the archive), load and lock it and then redirect the trap through that code segment. The real problem is that HackMaster was created because the trap redirection can cause the device to become unstable if multiple apps try to hook into the same trap - I can't remember if the instability occurs immediately or if the problem is related to removing your hack. Anyway. If you're going to do this it's very important that you also implement logic to search for third party hack managers and refuse to run if one is installed (because you're messing with the same infrastructure they are). You will also need to give a loud warning to the user that your hack cannot be used in conjunction with any other hack. Annoying, but it's the only option - one hack per device or only use HackMaster compatible apps. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
