this is a really useful prop… too bad it is not exposed in the PI
"use case for it"
OH Boy! us page lay people lock background objects all the time… once a subset
of elements are "locked down" design wise.. you don't what them moving about.
I'll be using this a lot now that I found it… But I guess the only UI in the
IDE is to switch to AB and toggle it in that column…
that definitely qualifies as "mystery meat UX"
is there an enhancement request to expose this in the property inspector for
all controls? till then we can add it to a tool set to toogle cantSelect for
the selectedObject()
On 8/27/17, 10:37 AM, "use-livecode on behalf of Monte Goulding via
use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of
use-livecode@lists.runrev.com> wrote:
>I don't think I've ever used the cantSelect property, and I've been having
a hard time trying to come up with a use case for it. Can you clue me in as to
a situation where this might be useful?
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
