-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key repeat rate on Linux, Wayland, Sway is interpreted inversely #777
Comments
Found the problem in client-toolkit. Working on PR. |
Yeah this is my bad, I read the wayland documentation wrong since the key repeat delay is in milliseconds. This should be fixed by Smithay/client-toolkit#62 |
At the exact same time, what are the chances ahah. |
Oh, you have already done it, great! |
Would it be possible to update the client toolkit dependency from 0.4 to the current 0.6 which includes this bugfix? |
cc @vberger |
This update is contained in the eventloop-2.0 refactor. Backporting the update to master branch would be a significant amount of work (it implies an upgrade of wayland-client, which was very largely breaking) that I am not willing to do a second time. However, I released SCTK 0.4.5 containing this fix, |
This is a copy of alacritty/alacritty#2041 . I initially reported it there but was pointed to testing it with winit directly.
I am using Linux with Wayland with Sway.
I am setting the key repetition rate in my sway config. Per
man 5 sway-input
:Alacritty is interpreting this value the wrong way.
When set to 1 I should observe one repetition per second and when set to 1000 I should observe 1000 repetitions per second. This works correctly in the browser I am typing this from (Firefox).
Alacritty seems to interpret the value as the number of milliseconds between repetitions giving me a lot of repetitions per second in the first case and 1 in the second case.
I can reproduce this problem with winit directly.
As explained in #776 (comment) I am using a https://github.com/tomaka/glutin example.
I am holding down the
f
key and from the console output I can see that the event appears with the wrong rate as described above.The text was updated successfully, but these errors were encountered: