In any case, what's wrong with the cantModify property, which would seem to be tailor-made for this?
Actually, the more I think about it, the more I like your original proposal of a custom property for this. CantModify has a more general purpose and would be (somewhat) overloaded serving in this capacity, I think.
regards,
Geoff Canyon [EMAIL PROTECTED]
On Sep 20, 2004, at 9:50 AM, [EMAIL PROTECTED] wrote:
Not so far as I can determine, Geoff. A Puzzler. But as Richard pointed out,
the 15 year tradition is that only toplevel stacks should be modifiable, and
it would assist plugins if this were honoured by RevTools.
/H
The cantmodify of (rev)Navigator is false, and I still don't have any
problems. Are you _sure_ the name isn't being checked? For example, the
Message Box can't be dropped on and it is both visible and modifiable.
regards,
Geoff Canyon
RevTools only checks for visibility and modifiability. If your stack is
immune, one must be true. The name of the stack is not trapped. This
is in 2.61 build 9.
/H
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
