>I'm using the ProtectOurDatabase() function ripped out
>of the DrMcCoy example app to prevent my apps from being
>deleted or beamed. Works great, except on the 3.5 devices.
>
>Both POSE (release rom) and a real IIIxe lose the application
>category, so it ends up in 'Unfiled' every time the app is run.
Yup. This is a bug in the launcher in 3.5: when you change a database's
attributes, it becomes unfiled. (The explanation of why is long and
convoluted.)
There are a few things you can do: first, don't set the bit if it is
already set! That'll probably take care of most of the problem. Unless
you've seen that the bit is off, just don't make the call to turn it on.
Secondly, if you're using somewhat recent tools (I think CodeWarrior r5 or
better, or any recent-ish prc-tools) then you can set the copy protect bit
at compile time. Most likely this'd be all you want to do; if someone
turns off the bit then it'll usually be a waste of time to turn it on again
since they've proved themselves savvy enough to turn it off and can be
expected to do so again if they want. So you can remove that database
attribute setting code alltogether, in most cases.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
