-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
[REQ] Use Volume buttons for manually changing speed #2657
Comments
done! https://github.com/cagnulein/qdomyos-zwift/actions/runs/11326729403 |
https://github.com/cagnulein/qdomyos-zwift/actions/runs/11326927837 in this i added also the inclination fix |
@cagnulein - Thank you for the changes, I have tested the build version you mentioned on your last comment and it fully works for me. I appreciate if you could send me a non-trial version. A couple comments:
|
yeah i guess your it's a side case, anyway i will keep this in mind
zwift is showing an average, qz the actual one. anyway you can try to set the zwift inclination gain to 0.5 that it helps to have a similar behaviour
yeah because you're changing the focus of the window |
Is your feature request related to a problem? Please describe.
I am currently using QZ for running since my treadmill doesn't have Bluetooth feature. I also don't have a foot pod. I am currently running using QZ Companion application on my Garmin watch and I change speed and inclination on my treadmill manually. Although it's working great, changing speed using the UI buttons on tiles is hard when you are running, also because it has "delay", so you end up clicking more than once sometimes. My idea to solve this problem is using the volume buttons on the phone to change the speed up and down.
Describe the solution you'd like
Volume buttons should manually set the speed according the the "step" defined on settings.
Describe alternatives you've considered
Having huge buttons on UI to change speed would also work, although volume buttons seems perfect solution.
Additional context
None
The text was updated successfully, but these errors were encountered: