Skip to content

feat: unassigned shortcuts#2737

Open
paxcut wants to merge 2 commits into
masterfrom
feature/unassigned_shortcuts
Open

feat: unassigned shortcuts#2737
paxcut wants to merge 2 commits into
masterfrom
feature/unassigned_shortcuts

Conversation

@paxcut
Copy link
Copy Markdown
Collaborator

@paxcut paxcut commented May 18, 2026

This PR attempt to address three problems that exist in the current shortcut implementation.

  1. If users find themselves having to use some menu item repeatedly they are unable to create a shortcut for it because menu items without shortcuts are not listed in the shortcut setting.
  2. Shortcut conflicts leave key sequences in an inconsistent state where the values displayed don't correspond to the actual shortcut key sequence.
  3. In order to "recycle" shortcuts used as defaults in ImHex one currently needs to assign some dummy shortcut to the action in question.

To address them keys that are not assigned to any key in the keyboard are defined. When these keys are part of a key sequence they make the sequence an unassigned shortcut. When a shortcut collision occurs, it is resolved by turning the shortcut being edited into an unassigned shortcut making its default sequence available to use elsewhere without a dummy.

paxcut added 2 commits May 18, 2026 15:45
This PR attempt to address three problems that exist in the current shortcut implementation.

1) If users find themselves having to use some menu item repeatedly they are unable to create a shortcut for it because menu items without shortcuts are not listed in the shortcut setting.
2) Shortcut conflicts leave key sequences in an inconsistent state where the values displayed don't correspond to the actual shortcut key sequence.
3) In order to "recycle" shortcuts used as defaults in ImHex one currently needs to assign some dummy shortcut to the action in question.

To address them keys that are not assigned to any key in the keyboard are defined. When these keys are part of a key sequence they make the sequence an unassigned shortcut. When a shortcut collision occurs, it is resolved by turning the shortcut being edited into an unassigned shortcut making its default sequence available to use elsewhere without a dummy.
… Unused function was missing changes if it started to get used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant