Skip to content
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

ROG Ally separate button mapping for mouse and gamepad mode #2549

Open
2 tasks done
lookbe opened this issue May 5, 2024 · 1 comment
Open
2 tasks done

ROG Ally separate button mapping for mouse and gamepad mode #2549

lookbe opened this issue May 5, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@lookbe
Copy link

lookbe commented May 5, 2024

Rules

  • I made myself familiar with the Readme, FAQ and Troubleshooting.
  • I understand that, if insufficient information will be provided, my issue will be closed without an answer.

Is your feature request related to a problem? Please describe

It would be great to have separate button mapping for mouse and gamepad mode. With current implementation button mapping override both mouse mode and gamepad mode, limiting use of paddle button on gameplay (set paddle button to another button and you lose all the brightness/sound/etc shortcut functionality). Accidental paddle button press on game session will also trigger the shortcut action when using default configuration.

Describe the solution you'd like

add another boolean check for reading separate app config value for mouse and gamepad, currently, boolean desktop check only set default value

Describe alternatives you've considered

for binding UI, just some toggle button to show what current binding option are active is enough

Device and Model

ROG Ally

Additional information.

No response

@seerge seerge added the enhancement New feature or request label May 6, 2024
@seerge
Copy link
Owner

seerge commented May 6, 2024

@lookbe hello, that's a valid request. But I need to find a good way to show it in UI, and still allow people to make universal binding (for both modes). As this is what majority will do, probably :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants