On 03/03/2016 01:09 AM, panagiotis merakos wrote:
Hi Mark,
I think the cantSelect property was always settable from within the Project
Browser. The reasons are discussed in
http://quality.livecode.com/show_bug.cgi?id=16416
Hope this helps,
Thanks - that does help. I have to say, though, that Richard's argument
in the QCC report makes more sense to me than the final decision. Why
not just put a checkbox in the property inspector? If you're not
changing the cantSelect by script then you have to bring up the PB to
get to the object anyway, so the property inspector is one click away,
and then cantSelect is like any other property.
I'm also curious now about the use case for cantSelect. I realize it's
not going away since it's always been there, but I'm having trouble
coming up with a scenario in which this is useful. My worry is that
we're putting a pretty obscure setting front and center in a primary
tool for stack design when screen real estate is already at a premium
(e.g. we're already overloading functions into the PB.
--
Mark Wieder
ahsoftw...@gmail.com
_______________________________________________
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
