Skip to content

feat!: generic key bindings#555

Open
robertwidfen wants to merge 1 commit into
Satty-org:mainfrom
robertwidfen:feat/generic_key_bindings
Open

feat!: generic key bindings#555
robertwidfen wants to merge 1 commit into
Satty-org:mainfrom
robertwidfen:feat/generic_key_bindings

Conversation

@robertwidfen

Copy link
Copy Markdown
Collaborator

See issue #450.

Changes syntax for [keybinds] section in config file to

"key" = "tool-or-command"

Also adds:

  • bindings for all toolbar buttons
  • commands for size selection
  • automatic hint generation for all buttons

Removes:

  • layout independent key bindings - instead bind what you want
  • single letter binding restriction

Old style is still supported but will generate deprecation warnings.

The old code always sent key events into the IME handling before they were processed as key event. Thus there were two places for bindings, bindings with a modifier and single letter bindings. But IME is for text input, thus it is now only activated for the text tool.

See issue Satty-org#450.

Changes syntax for [keybinds] section in config file to

    "key" = "tool-or-command"

Also adds:
- bindings for all toolbar buttons
- commands for size selection
- automatic hint generation for all buttons

Removes:
- layout independent key bindings - instead bind what you want
- single letter binding restriction

Old style is still supported but will generate deprecation warnings.

The old code always sent key events into the IME handling before
they were processed as key event.  Thus there were two places for
bindings, bindings with a modifier and single letter bindings.
But IME is for text input, thus it is now only activated for
the text tool.
@RobertMueller2

Copy link
Copy Markdown
Member

Good work, code looks good to me with just a few tiny inline remarks. Not that many for such a big change. What I tested worked. Difficult to try out everything 😄

IME still works as far as I can tell. But I'm not the greatest expert for it. I'm not sure if I should say "it still works", perhaps somebody else sees this and can confirm this.

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.

2 participants