-
-
Notifications
You must be signed in to change notification settings - Fork 480
Easier navigation of library #2051
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
Comments
These improvements were already made and will be available on next release. |
I'm using the latest Heroic Games Launcher release and seeing this same issue when moving down using the d-pad or analogue stick. |
are you on steam deck? |
Yes. If a title is selected on the bottom row but the bottom row isn't fully in view, I need to press down twice. This then moves the next row into view (but not 100%) meaning going down another row requires another two presses, and so on. |
we currently rely and the browser's native spatial navigation and don't have too much control on how much it scrolls when moving, I'm not sure if we can fix that completely, I'll do some tests (I'll reopen this issue since that part of the original problem is not addressed) |
This should be fixed by #3354 |
Closing because that PR got merged today. This will be included in the next release |
Problem description
On Steam Deck right now navigating the library is not otpimal when using the analogs/directional buttons: moving between adiacent games left to right and viceversa only requires on button press. Moving up and down requires instead between 2 to 3 button presses: two if the both titles' images are fully displayed into the screen, three if the title's image we moved to is partially cut. This makes for an unpleasant experience when quickly moving up and down the library.
Feature description
Moving up and down should be a one press action, regardless of the direction. The selection of the download button, when using steam deck's controller, could be skipped.
Alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: