Well, Mouseleave works for my current use case. And, testing… mouserelease is simple enough to script
on mouseRelease set the hilitedlines of me to 0 end mouseRelease That said. I’m not sure a new property is needed. IMHO I think the default behavior should be that if you click on white space in the field, lines are unhilited. This is very intuitive for any user/use case, because hilites occur when the object you mouse on is under the mouse. So having the hilite go away when click on white space makes “natural sense” Of course as Mike says, if the field container more lines than are visible, one has do something else altogether. And if HQ doesn’t want to change it… I can live with mouseRelease and mouse leave ... On 4/26/16, 7:14 AM, "use-livecode on behalf of Richard Gaskin" <use-livecode-boun...@lists.runrev.com on behalf of ambassa...@fourthworld.com> wrote: >What should the property be called? This: > > set the clicksOutsideTextClearHilites of fld 1 to true > >...would be descriptive, but horrible (though if inclined one could make >a behavior script with getProp/setProp handlers using the script above >and have that today <g>). > >Any other suggestions? _______________________________________________ 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
