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

Simple Keybinds Override More Complex Keybinds #788

Open
vexir opened this issue Dec 25, 2023 · 2 comments
Open

Simple Keybinds Override More Complex Keybinds #788

vexir opened this issue Dec 25, 2023 · 2 comments
Assignees
Labels
bug Something don't work

Comments

@vexir
Copy link

vexir commented Dec 25, 2023

Reproduced with only Dominos and config running.

Addon Version
10.2.1-retail

World of Warcraft Version
Retail, latest.

Issue
I have a button bound to CMD+1, and another button bound to CMD+SHIFT+1. These keybinds were made through the Dominos keybind feature. When I hit "CMD+SHIFT+1", the button for CMD+1 is pressed instead.

@vexir
Copy link
Author

vexir commented Dec 25, 2023

@Tuller interestingly, the way to fix this seems to be to go into Blizzard's menu for key binds and set it there. I noticed that the ordering is different.

When bound via Dominos, the key showed up as CMD+SHIFT+1, but when I press the same keybind in the Blizzard menu, it switches to SHIFT+CMD+1. What's interesting is that I'm actually pressing CMD+SHIFT+1 in that order, so theoretically Dominos is more accurate, but this for some reason causes the game to not register the keybind.

@Tuller Tuller added the bug Something don't work label Jan 8, 2024
@Tuller
Copy link
Member

Tuller commented Feb 5, 2024

This might specifically be an issue with LibKeyBound, which Dominos uses:
https://www.curseforge.com/wow/addons/libkeybound-1-0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something don't work
Projects
None yet
Development

No branches or pull requests

2 participants