On 2016-03-04 02:49, Richard Gaskin wrote:
AFAIK this has always been how it works. In fact I discussed this with Dr. Raney shortly after if was implemented, and in his view it works as spec'd: when you mouseDown anywhere in browser mode it doesn't do marquee select, so when an individual object is set to browser mode it does the same thing.
Given the intent of the property (to make objects run in browse mode when another tool is actually selected) I"m not sure it could work any other way.
It is the card which provides the marquee selection rect to select multiple objects when in pointer tool mode, then individual objects defer to the common control base class to provide the click to select behavior in pointer tool mode.
When you set the cantSelect of an object, that object will then see the tool as browse, so when you click on it that causes the normal browse mode event handling to take place - which is defined on a per-object basis.
Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps _______________________________________________ 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
