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 > On Nov 10, 2017, at 14:05 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hold up on that. I am seeing that when swiping down through several records, > the data I am getting is for the first record touched, and NOT the one I am > currently pointing at! I need to find out why. I think I need the > mouseControl. > > Bob S > > >> On Nov 10, 2017, at 13:54 , Bob Sneidar via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Hi all. >> >> A while back I had a go at setting the tooltip when pointing at a datagrid >> element, but ran into some difficulties when scrolling. With Trevor Devore's >> assistance, I came up with a reliable way to do this. Enjoy. > > <snip> _______________________________________________ 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
