Unable to assign any "select next window" with a combination "hold" button shortcut that conflicts with another shortcut that shares an individual "hold" button #3288
Comments
phazei
changed the title
|
Same issue here. I wanted to assign ⌘+⌥+^+⇧ + ⇥ to the Shortcut 1, and I had this dialog: Shortcut is already used in "select next window", which I assume means there was a conflict with Shortcut 2's assigned keystroke: ⌥ + ⇥. Perhaps this bug is hard to fix, but at least having an option to reset the keys (and by reset I mean: blank) would makes it less tedious than the current weird method. |
|
This bug is not hard to fix, it probably only would take a couple lines of code, but the dev probably hasn't even looked at this issue :/ |
|
I really walked into that one... Though I really couldn't use my mac without this util. I've never done swift, but at least it's not obj-c, I've found that with Claude, the language really doesn't matter anymore, just the decades of experience. Guess I'll take a look this weekend. |
|
Looks like I had a couple hours this evening! |
Describe the bug
The conflict checker checks to see if any individual "Hold" key exists somewhere else even if it's used in combination. If an individual key from combo "Hold" key is used individually in another shortcut, it fails.
Examples:
Suppose I use (⌥) + in shortcut one.
Then any other shortcut that uses (⌥+⌘)+ doesn't work
It happens with any individual "Hold" key.
For ex:
⇧ + J
Then I try
⇧⌥ + J, it gives a conflict error.
There is a work around currently:
unassign ⇧ + J
assign ⇧⌥ + J, no conflict
reassign ⇧ + J, no conflict
Then both of them work perfectly as expected.
Your environment
The text was updated successfully, but these errors were encountered: