Implement key map overrides for jogging.

[aaronse]

Enable Users to optionally adapt/define/suppress key shortcuts for their machine and keyboard setups.

Sent this pull request to better help communicate the ask, and a possible solution approach.

[luc-github]

Nice - indeed the shortkeys management need improvement
Here my comments :

• I think the available controls for shortkey should be listed in array because user has no idea of id of different controls , using a search may not work if the panel is not visible and we need to configure key in settings
• Shortkeys should be auto detected (ask user to type them) or listed because user does not know what is the syntax of keys neither
• instead of using string which is ok when you know all use a ui like panels: with json format:
  name (fixed) which could be the id of control but it may be meaning less for user - TBD
  the id of control to be controled (fixed by above list of bullet 1), and the shortcut
• Use the json definition from the begining so user can see all keys configured in settings
• Reflect the help using the json definition would then be very easy even after update
• doing this will allow to implement it for cnc with more / less than 3 motors

Has you did the shortcut management already from API point of view it just need an additionnal list type (shortkeys) to be displayed properly and use json and parse them

Let me know what do you think ,

[V1EngineeringInc]

The other odd thing about the physical keyboard bindings is homing.

So when typing in a terminal, Using X, Y, or Z, homes the machine. We tend to use the terminal a lot. Would it make more sense to use Alt+X,Y, Z to home?

[luc-github]

there is no current support for combination key shortcut, I am not sure it will be address in this PR, original implementation was as simple as possible - waiting for feedback and this PR is the first one I got

@aaronse sorry I have just make some change for current consistency issue raised by @V1EngineeringInc - just rebase your fork should fix the conflict - you do not need to rebuild package - it is better to build only at the end because need changing version as well, so you can leave it to me

[aaronse]

Hmm, wasn't sure how to reopen/continue this pull request after rebasing to absorb recent edits. Ended up creating #284 which references this one. Will continue discussion there unless you say otherwise. Cheers!

[luc-github]

sure - thank you