KM Engine causes issues

Hey all, I apparently made some changes to KM that I did not intended to do. All the time I am opening up KM it alters with MacOS which continues even when KM is closed until I reboot the system. One example that I can always see: The App switcher menu (CMD+tab) has a greenish background instead of grey. Some keys cause unexpected behaviors / menus to pop up.

One thing I found helped is clicking on File - Quit Engine. But I would like to understand what exactly I did and how to permanently fixed it. Another thing is that the font in the app became huge.

In case this helps: I was using via to configure my keyboard while this happened apparently.

I was able to fix a view things. The app switcher was due to the macro "Activate Application Switcher", which I have no idea why it was activated. I also reset some keyboard settings.

What remains is that the right column (that includes the macros details) remains in large text. I changed the text size in the settings menu but that only effected the left and middle column. I am not sure but I think a macro also affects Bluetooth settings somehow.

Any advice would be appreciated.

Thank you
Dennis

Have you looked inside the KM Engine Log file? That will tell you exactly what was triggered. It seems possible that you have activated a Macro Group without realizing it, but you need to check your logs to see what "unexpected behaviour" was actually occurring.

I'm unable to understand what that means. Maybe you should upload a screenshot. Or maybe someone else will understand what you mean. I'm not the sharpest tack on this website.

Are you perhaps in viewing rather than editing mode? Try going to ViewStart Editing Macros.

image

You are likely correct. You have a great imagination when it comes to reading people's words. You are a very sharp tack.

Not sure about very sharp, but I try my best.

Thank you both it really helped. I was indeed not in editing mode. Previously I was not even aware that you can go into viewing mode.

Via the history keys I found another macro that I did apparently activated. Well looks all is sorted now - hopefully :smiley: