The limitations of KM Conflict Palettes is probably the entire reason I've been seeking a better input method like the one in this post.
Maybe a more in-depth explanation of these palettes from yourself or @Frankb would help.
I would explain it but I don't understand them beyond the default Conflict Palette – which I think is so-so but not great.
The reason being that the letter-by-letter selection option in the default Conflict Palette breaks down when the names of your macros start getting too similar.
For example, here are the names of some of my macros and what KM expects me to press after the initial 'I':
Expected letters have been bolded and capitalize for detail:
InsErt Row Above
InsErt Row Below
InsTall Beta Build
InsTall UAT build
I > E to Insert Row? I > R would be more intuitive.
I > T to Install Beta? I > B works better.
These resolutions makes no sense so then you have to spend too much time trying to find the next letter in the Conflict Palette – for which the rule by default is – "resolve to the next character that differs".
Honestly, if KM could change this Conflict Palette character resolution method then I wouldn't need any of the custom macros we've made in this thread.
In addition to the default, it would be useful to have these user configurable options when resolving macro names in Conflict Palettes:
- Resolve to the next character after a space (if one does not exist, then use the default)
- Resolve to the next capital letter (if one does not exist, then use the default)
Using #1, my Conflict Palette would look like this after inputting the first 'I':
Insert Row Above
Insert Row Below
Install Beta Build
Install UAT build
Much better – because now "Insert Row Above" is now I>R>A, which is easier to remember.
This would allow me to think about keypresses as I have named my macros and not by some heuristic that breaks down with macros too similarly named.
Notice this is the same mechanism that @AIvaro wants to use. It blocks input and you can enter a sequence to launch a macro.
I'm not sure where you'd specify this in KM if it were an option. Preferences?
So, while I definitely have issues with the default Conflict Palette – I would be interested to see how a custom one would address this issue