Erratic and inconvenient mousewheel scrolling

[nuenuewei]

Bug Report

Scrolling is jerky and rapidly accelerates from extremely slow to whole pages at once. Scrolling gets "snagged" on parts of chats and requires overshooting to pass these snags. Scrolling has slow acceleration and deceleration animations, leaving the text less readable until it comes to a stop.

Steps to Reproduce

1. Open any sufficiently long chat
2. Scroll up and down using mouse wheel slowly(one notch at a time no faster than about once per second)
3. Scroll around using mouse wheel slightly more quickly(several notches at once)
4. Scroll one notch, then another in succession(about twice per second).

In step 2 the window will scroll very slowly- and there are apparently some anchors in chats that "snag" and won't scroll past at all unless you do step 3. In step 3 the window will scroll as much as several pages, far overshooting what you intended. In step 4, the scrolling will accelerate dramatically between the first and second notches, again greatly overshooting the expected output, and also snagging on these anchors. In all cases, mouse scrolling has a long acceleration and deceleration that interferes with readability.

Expected Behavior: Scrolling that directly and consistently correlates to mousewheel movement and makes scrolling at a human reading speed easy. Scrolling that is smooth and does not snag or snap to parts of the text. Scrolling that begins and completes quickly instead of having long acceleration and deceleration- we read text best when it's not moving.

I get the feeling that some of these behaviors are intentional, so this can also be taken as feedback- it feels really bad to use a mouse wheel in this program, in general.

Your Environment:

• GPT4All version (if applicable): 3.0
• Operating System: W10 Pro 22H2
• Chat model used (if applicable): any

[cosmic-snow]

I think this has already been fixed for the next version with #2555.

But I'd say you should check it again when that is released and report back.

[nuenuewei]

I think this has already been fixed for the next version with #2555.

But I'd say you should check it again when that is released and report back.

Thanks for letting me know. I will do as advised.