For this use case, there are 4 list fields that want to retain their hilited lines as the user traverses through them and 2 that do not…
So it was easy enough to just do this On mouseleave Set the hilited lines of me to none End mouseLeave For those two fields. And this is even better since it requires no actual action. I still think it a bug and I wasted a lot of time trying to determine what I was doing wrong. Certainly a newbie will be very frustrated if they want to trap for mouseup or down when it works for all other field types and all other objects. One then has to decide what the default behavior should be. See: http://quality.livecode.com/show_bug.cgi?id=17517 Proposed that (as it is, IMHO, what one intuitively expects to happen) Click on the field with no line beneath the mouse, the engine should: 1) set the hilited lines of the field to none. 2) fire any script that is attached to mouseup or down. 3) if the script is looking for hilitedlines, the engine returns “0” I can’t imagine any possible backwards compatibility issues there. BR On 4/25/16, 8:24 AM, "use-livecode on behalf of Mark Schonewille" <use-livecode-boun...@lists.runrev.com on behalf of m.schonewi...@economy-x-talk.com> wrote: >I also consider this a bug, but it has always been like in >Revolution/MetaCard. > >You may solve this problem by using mouseDown messages or by setting the >lockText to true. This isn't always a good solution, but it is worth a try. _______________________________________________ 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
