Touchpad scrolling too fast -- should act in precision mode #1421

@zadjii-msft commented on GitHub (May 30, 2019):

I mean, I guess we could figure out how to configure how much we scroll by when the user scrolls. That seems like it should be something the system configures however.

Maybe we just need to look up some value from the system to determine how much to scroll by.

@zadjii-msft commented on GitHub (May 30, 2019): I mean, I guess we could figure out how to configure how much we scroll by when the user scrolls. That seems like it should be something the system configures however. Maybe we just need to look up some value from the system to determine how much to scroll by.

claunia commented

@DHowett-MSFT commented on GitHub (May 30, 2019):

We should probably do line-by-line scrolling on touchpads to mimic precision scrolling. We should almost certainly make sure velocity coasting works when we do this.

@DHowett-MSFT commented on GitHub (May 30, 2019): We should probably do line-by-line scrolling on touchpads to mimic precision scrolling. We should almost certainly make sure velocity coasting works when we do this.

claunia commented

@warpdesign commented on GitHub (Jun 22, 2019):

Same problem here on a Surface Book.

I think it should be possible to scroll by as little as one line if movement is very small.

Also, having some kind of velocity and not have the scrolling immediately stop as soon as the user stops scrolling would make the Terminal app behave more like other (UWP) apps.

@warpdesign commented on GitHub (Jun 22, 2019): Same problem here on a Surface Book. I think it should be possible to scroll by as little as one line if movement is very small. Also, having some kind of velocity and not have the scrolling immediately stop as soon as the user stops scrolling would make the Terminal app behave more like other (UWP) apps.

claunia commented

@ZZYSonny commented on GitHub (Aug 4, 2019):

Both line by line and pixel by pixel are pretty nice for me. Pixel by pixel is "nicer" but smooth scroll could result in a efficiency problem in terminal.

For now I think we should fix scroll too fast problem. The gesture to scroll a few lines in a browser could scroll an entire page in Windows Terminal, which makes the scrolling process unreadable and hard to locate. Probably do some translation, like scrolling one line in windows terminal = scrolling some lines in UWP. At least make it slower.

@ZZYSonny commented on GitHub (Aug 4, 2019): Both line by line and pixel by pixel are pretty nice for me. Pixel by pixel is "nicer" but smooth scroll could result in a efficiency problem in terminal. For now I think we should fix scroll too fast problem. The gesture to scroll a few lines in a browser could scroll an entire page in Windows Terminal, which makes the scrolling process unreadable and hard to locate. Probably do some translation, like scrolling one line in windows terminal = scrolling some lines in UWP. At least make it slower.

claunia commented

@liuguangyong93 commented on GitHub (Sep 14, 2019):

i think its scroll fast，Seriously affect user experience！！

@liuguangyong93 commented on GitHub (Sep 14, 2019): i think its scroll fast，Seriously affect user experience！！

claunia commented

@PaulBendall commented on GitHub (Oct 31, 2019):

Any update on this issue? Its been listed for a while and makes terminal a pretty poor experience on laptops with touchpads include Microsoft's own Surface range (e.g Surface Book 2)

@PaulBendall commented on GitHub (Oct 31, 2019): Any update on this issue? Its been listed for a while and makes terminal a pretty poor experience on laptops with touchpads include Microsoft's own Surface range (e.g Surface Book 2)

claunia commented

@zadjii-msft commented on GitHub (Oct 31, 2019):

@PaulBendall Nope. We'll make sure to post on this thread when we do find some time to address it. It's marked for "Terminal 1.0", so we plan on fixing this before the 1.0 release, but we don't have a more specific timetable than that. If someone's passionate about this bug and wants to take a crack at fixing it themselves, we'd be more than happy to review a PR from the community 😊

@zadjii-msft commented on GitHub (Oct 31, 2019): @PaulBendall Nope. We'll make sure to post on this thread when we do find some time to address it. It's marked for "Terminal 1.0", so we plan on fixing this before the 1.0 release, but we don't have a more specific timetable than that. If someone's passionate about this bug and wants to take a crack at fixing it themselves, we'd be more than happy to review a PR from the community 😊

claunia commented

@jboeshart commented on GitHub (Nov 15, 2019):

Upvote on this, touchpad scrolling on Surface Book 2 (and would assume other Surface devices) is really bad.

@jboeshart commented on GitHub (Nov 15, 2019): Upvote on this, touchpad scrolling on Surface Book 2 (and would assume other Surface devices) is really bad.

claunia commented

@piratetub commented on GitHub (Nov 17, 2019):

I have a precision Touchpad and I can vouch that the scrolling is so fast that I can't use Windows Terminal with my Touchpad at all. I have to rely on a touchscreen to scroll.
Also, the general scrolling behavior does not adhere to the general UWP scrolling behavior- no smooth scrolling. The team should consider changing the behavior to at least match the classic console's, which is usable at the least.

@piratetub commented on GitHub (Nov 17, 2019): I have a precision Touchpad and I can vouch that the scrolling is so fast that I can't use _Windows Terminal_ with my Touchpad at all. I have to rely on a touchscreen to scroll. Also, the general scrolling behavior does not adhere to the general UWP scrolling behavior- no smooth scrolling. The team should consider changing the behavior to at least match the classic console's, which is usable at the least.

claunia commented

@hannesne commented on GitHub (Nov 27, 2019):

I've done a pull request to make the number of lines that is scolled at a time configurable in the settings file. Default was previously hard coded at 4, with a todo in the comment. On my Surfacebook I set it to 1 and it works real nice. Pull Request is #3575 Incidentally setting the number of lines to scroll to a negative value enables reverse scrolling. cc @zadjii-msft

@hannesne commented on GitHub (Nov 27, 2019): I've done a pull request to make the number of lines that is scolled at a time configurable in the settings file. Default was previously hard coded at 4, with a todo in the comment. On my Surfacebook I set it to 1 and it works real nice. Pull Request is #3575 Incidentally setting the number of lines to scroll to a negative value enables reverse scrolling. cc @zadjii-msft

claunia commented

https://gist.github.com/ovcharik/20af27323514fcf2b116f9cfaad420f4

@ovcharik commented on GitHub (Dec 4, 2019):

Not sure that is still relevant. But as temponary solution it is possible use AutoHotkey script.

@ovcharik commented on GitHub (Dec 4, 2019): Not sure that is still relevant. But as temponary solution it is possible use [AutoHotkey](https://www.autohotkey.com/) script. https://gist.github.com/ovcharik/20af27323514fcf2b116f9cfaad420f4

claunia commented

@davidwparker commented on GitHub (Dec 27, 2019):

Nice PR @hannesne - is there any update on this? I'm assuming (due to holidays, etc), the earliest we would see this would be next year?

@davidwparker commented on GitHub (Dec 27, 2019): Nice PR @hannesne - is there any update on this? I'm assuming (due to holidays, etc), the earliest we would see this would be next year?

claunia commented

@zadjii-msft commented on GitHub (Dec 30, 2019):

@davidwparker Correct - I don't think we're planning on shipping an update today, so it's definitely not landing till the next decade :P

@zadjii-msft commented on GitHub (Dec 30, 2019): @davidwparker Correct - I don't think we're planning on shipping an update _today_, so it's definitely not landing till the next decade :P

claunia commented

@hannesne commented on GitHub (Jan 5, 2020):

@davidwparker PR only needs approval from @carlos-zamora, before being merged.

@hannesne commented on GitHub (Jan 5, 2020): @davidwparker PR only needs approval from @carlos-zamora, before being merged.

claunia commented

@joeyaiello commented on GitHub (Jan 13, 2020):

Just wanted to pile on that, while setting the number of lines on scroll is very helpful, smooth scrolling (a la what I get in most browsers) is what I'm really looking for. Touchpad/scroll wheel is a bigger deal for me than touchscreen, but that would be sweet too.

@joeyaiello commented on GitHub (Jan 13, 2020): Just wanted to pile on that, while setting the number of lines on scroll is very helpful, smooth scrolling (a la what I get in most browsers) is what I'm really looking for. Touchpad/scroll wheel is a bigger deal for me than touchscreen, but that would be sweet too.

claunia commented

@DHowett-MSFT commented on GitHub (Jan 13, 2020):

Yes, we just need somebody who knows anything about the direct input/direct manipulation APIs to take a crack at it 😄

@DHowett-MSFT commented on GitHub (Jan 13, 2020): Yes, we just need somebody who knows anything about the direct input/direct manipulation APIs to take a crack at it :smile:

claunia commented

@mahmoudajawad commented on GitHub (Jan 15, 2020):

So, this didn't make it in v0.8 arrived today. Can we expect it with next release?

@mahmoudajawad commented on GitHub (Jan 15, 2020): So, this didn't make it in v0.8 arrived today. Can we expect it with next release?

claunia commented