BUG the target returns the wrong control in a scrolled datagrid

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

BUG the target returns the wrong control in a scrolled datagrid

** Clarence P Martin ** via use-livecode
Hi all.

Remember if you will someone pointed out to me that I can get the target in a mouseEnter handler in a datagrid to determine the name of the control I was pointing at? Works great... so long as the datagrid has not scrolled! If you scroll you get a control for a completely different row!

Unless someone comes up with an explaination why it *should* work that way, I will submit a bug report.

Bob S



_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BUG the target returns the wrong control in a scrolled datagrid

** Clarence P Martin ** via use-livecode
Confirmed here.


If you populate a DG with several lines, something like:


on mouseEnter
  put the target
end mouseEnter


will give scatterbrained results. I had thought at first that, if the scroll was in the middle of its range, say, and I moved the cursor into the third visible line, I might see field "Col 1 0003".


But, no rhyme or reason.


Craig



-----Original Message-----
From: Bob Sneidar via use-livecode <[hidden email]>
To: How to use LiveCode <[hidden email]>
Cc: Bob Sneidar <[hidden email]>
Sent: Wed, Aug 9, 2017 4:09 pm
Subject: BUG the target returns the wrong control in a scrolled datagrid

Hi all.

Remember if you will someone pointed out to me that I can get the target in a mouseEnter handler in a datagrid to determine the name of the control I was pointing at? Works great... so long as the datagrid has not scrolled! If you scroll you get a control for a completely different row!

Unless someone comes up with an explaination why it *should* work that way, I will submit a bug report.

Bob S



_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Loading...