Since installing KM 9, some of the macros will not execute using the lower case conflict letter unless holding down the shift key while pressing the highlighted letter for the conflict palette, or selecting it with the mouse.
Trigger a Macro group, which displays an n) ordered list, with conflicts in the names.
Some of the names:
15) UEXT conflict E
20) UCTT conflict C
I'd expect to press , "u" (does work), "e" (does not work) as I did with KM 8. However "E" does work.
In another example, I'm using
All Caps conflict C
All Maps conflict M
, "c" (works), "m" works.
I've tried: 1) swapping triggers between functional and non functional groups, 2) changing conflict key characters with the issue, duplicating the macros, etc. Nothing helps macros that are "broken", and nothing I do can replicate the bug in the macro group that works.
I've tried creating a new macro group, and I see the same behavior. If I move the macros to the group that does work, I see a second bug where the conflict character highlighted is the same first character that causes the conflict in the first place.
UEXT (Conflict U), (Second Conflict E)
UCTT (Conflict U), (Second Conflict C)
Thank you for the testing you performed. Both issues still persist intermittently through another hour of testing.
As I delete some of the extra macros, the "U" conflict group goes from highlighting all four initial "U" characters in the conflict palette, to what I show in the last graphic. I tried deleting the macros one by one, but it results in repeated crashing of the KM engine.
Lower case letters do not trigger macros in conflict palette, but uppercase characters do:
The conflict palette eventually accepts lower case letters, when all other macros in the macro group are deleted. Also note: when creating this test group, the initial "U" in the conflict palette are blue. I neglected to get a screen shot of this.
Could the "U" near the right margin in the palette be a clue to in appropriate configuration of the conflict palette?
Not likely. But to troubleshoot, I'd create a NEW Macro Group, and a few NEW Macros to model the behavior you are seeing. In fact, if you can do this without revealing any sensitive info, then you can upload the new MG and Macros for us to test.
BTW, what versions of KM and macOS are you running?