When defining multi keys sequences, i frequently see messages saying "combination already in use", which is mostly not the case. It seems, that the
error message is fired prematurely, before the second key is entered. There are no red double entries, so i assume that this is a small bug.
What are the steps to reproduce this?
For example, make a new multi key combination using Alt-L-A, which could be some simple go command like "Go L:\path01". If you want to make a command for another path,
using "Alt-L-B", the error message would show, even if there is no combination using exactly the same sequence. The error message is thrown after the whole sequence has been
defined & is confirmed.
It doesn't do that here. Are you sure you don't have an Alt-L hotkey defined? Use the filter at the bottom of the list to check.
I used the filter for that, of course, & i saw it happening at least a dozen times. Isn't it supposed to show the double entries in a red font? I've just finishes a whole series
of commands based on AltGr-L, plus a second key, like AltGr-L-M, AltGr-L-N, AltGr-L-P, but i also saw it with the normal Alt key. The AltGr key is quite the same as pushing
Right-Alt-Control, by the way.
Here is an image, showing my current AltGr/Strg-Alt multi keys. When i made them, each one was claimed to be already present.
I forgot to mention, that i also saw it happening with two part multi keys, not only three part ones, so that might not be the reason.
I just created these hotkeys, one after the other, and didn't see any warnings about existing hotkeys:
Hmm, i think i have a hint, what caused it. There was a plain AltGr-L hotkey, something like what you have suggested. I have deleted it, & the error message
isn't showing anymore. I was assumig, that it woul not interfere with my other hotkeys, since it was deactivated (not checked). So, it looks like also deactivated
keys are checked for double entries, also they don't generate the ususal red font duplicates. Thanks Leo.