Feature Request: Keymap Inheritance
Apologies if this can be done currently.
I'd like to request a feature to allow Keymaps to behave in a manner similar to the OO Programming Inheritance model. The idea being you could have a base keymap from which you create a child keymap that can alter or add keys to it's parent. Here is an example of how I would use such a feature.
The 3 is setup to be sent to all my characters in my FTL setup and I use it in multiple teams. Unfortunately I have the 3 key set to Death Grip on my DK team. Ideally I want Death Grip to be round robin, but that would require me to either create a separate keymap for my Death Knights so that I could make that key round robin, or I would need to make a separate group of keymaps to handle keys that are round robin in some groups and not in others in addition to any keymaps that are shared between all groups.
Why don't I just make separate keymaps for all my groups? I tend to jump around my groups and it's annoying when I have added something like Jamba Item Use keys in one group, but I haven't added the keys into that groups keymaps in ISBoxer.
In the above example, the round robin wuld be solved with inherited keymaps in the following manner. There would be a master key map that would have the 3 key set to broadcast to all slaves. This would work on 90% of my teams. There would then be a second keymap derived from the master keymap. In this keymap there would we be a mapping for the 3 key that overrides the parent keymap's mapping of 3 and sets it to instead be a round robin. While I still need a separate keymap for the DKs, it would only need to contain the changes to key 3 as all the other keymappings are inherited. If I were to add a mapping for Ctrl-H for some reason, the DKs would get it for free. If I needed to make the 4 key round robin, I could simply change the DK map for the 4 key only.
I hope this makes sense. If you need clarification on anything, don't hesitate to ask.
- Souca -
Connect With Us