Closed ghost closed 2 years ago
This issue is not limited to touchpads, I'm having the same problem with a regular mouse scroll wheel on Windows for the list-box control. On my system (Windows 11) scrolling any racket list-box does not work correctly, it doesn't reach the bottom of the list. Somehow the problem disappears when resizing the list-box or maximizing the parent window. This is becoming a problem as many of our internal apps use the list-box. Our staff has been complaining about this problem for a while. I'm currently looking for a version of Racket that doesn't exhibit the problem. I have tried 8.6 release, 8.6.0.2 and 8.6.0.9, and all have the same scrolling problem.
I found a way to temporarily fix the problem by clicking once on the scrollbar. List-box exhibits the same problem if resized.
On line 414 of "share/pkgs/gui-lib/mred/private/wx/win32/list-box.rkt", there's a (unless (= c i) ...)
. I don't know why that's there, and I can't make any sense of it at the moment. Does scrolling work better if you change (= c i)
to just #f
?
I'll give it a try and get back to you. Thanks Matthew!
Good news: it seems to be fixing the problem on both my Win systems (win11 and win10). Scrolling still locks up for maybe 50-100ms every couple wheel turns, but it works all the way to the end. Thanks again.
Ok, thanks for trying it! I'll push this repair.
Matt I'm getting this error once in a while within DrRacket since the temporary patch:
scroll-line-location method of text%: expects argument of type
Dr. Racket version: 8.0 OS: Windows 10 pro 20H2 Machine: Packard Bell Easynote LV 11 HC
How to reproduce the problem
The list will not scroll all the way to the end, but it will get stuck near the beginning. On the other hand, if you use the scrollbar (in the "Currently installed" tab) and go to the end, then try to two-finger scroll to the beginning, the list will get stuck in nearly the same place; If you scroll with the scrollbar to the end of the list in the "Available from catalog" tab then two-finger scroll all the way up, it seems that two-finger scrolling starts to work properly.
This issue seems to be related to #246 and #233.
Here is a gif that shows the issue in practice: