>
>Is there some problem that arises because the bits aren't cleared until the
>database opens?
Well yes, (but probably you have enough to think about without worrying
about hacks, too.)
In my Pop hack, the user pops up a memu by tap dragging in the control
area. I needed a way to block them from re-activating the hack if they
already had the list opened on the screen, so I was using the opened
or closed status of the Pop database as a test to see whether it was
safe to act or not. Thus, if there was a crash when Pop was active,
it would never open again, since the database header was left marked
"open".
So I also had to add a "repair" mode which would fix the dmHdrAttrOpen bit
under some other condition which the user could manually activate.
Obviously there are other ways I could have used to test whether or not
it was safe for Pop to activate, but it seemed the best solution at the
time because I didn't know how to temporarily un-patch the trap used
for activation, and I didn't want to use yet another Feature...
Rick
