NVM It seems like wait with messages unlocks messages! So what I am seeing is the result of the last mouse enter working last to first in the chronological order the mouseEnter messages were sent.
Bob S > On Nov 10, 2017, at 14:58 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > OK I am seeing a very curious thing. This may be the way it's supposed to > work, and maybe not. I have this in a handler: > > on mouseEnter > lock messages > wait 30 ticks with messages > unlock messages > put word 2 of the mouseControl into tControlNum > end mouseEnter > > Now when I move the mouse over a series of datagrid rows, you would *think* > that tControlNum would be the number of the control I am currently pointing > at. You would be wrong. It's the number of the control I FIRST POINTED AT! > Now that can't be right can it?? > > Bob S _______________________________________________ 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
