This macro stop working after the last KM update. Is there a fix?
Define "not working". It doesn't trigger? Or it triggers and does the wrong thing? What wrong thing does it do?
Did you check the Engine.log file to see if it triggered or if there was an error? Did you run the Interactive Help feature in the KM Editor to help understand the issue?
From the Engine Log it looks like it triggered, but I hear nothing. This did work until the last KM update.
You don't hear "on/off" or you don't even hear "Caps Lock"?
You should turn on the debugger and watch it execute your macro line by line. Tell me if it reaches the two "Speak" actions or not.
Sorry to ask this, but is your system volume set to zero?
It started working again. I have no idea why. All good though now. Thanks.
Don't worry about being embarrassed if you made a mistake. We all make mistakes. In fact, I would say 20% of everything I say is wrong. We just have to learn to live with mistakes.
After any macOS upgrade, I strongly advise you to restart a further time. I have frequently seen cases where the system is not in a stable state after an upgrade.
Perhaps that was your problem.
1 Like
This macro is not working like it did before. I cannot get the Caps Key Off notification to work. I attached the macro. Hopefully someone can figure out how to make it work. Thanks.
Caps Lock Notification.kmmacros (7.3 KB)
It works perfectly for me, once I change the trigger to my own keyboard.
There is, however, a small bug in your code, which might be related to your problem. You are using the trigger "is down" which means it will trigger a hundred times per second when you press Caps Lock. Why do you want it to trigger 100 times per second? If you change the trigger to "is pressed" that might make you macro behave better. Any macro that is triggered 100 times per second will likely end up with the KM Engine aborting due to having over 50 simultaneous macros.
But my real guess is that you have some third party utility software that's interfering with your key trigger, since your macro works fine for me, apart from the bug mentioned above.
@Airy. I found this macro on the KM site. It was created 9 years ago. Maybe someone here could create a new updated version of this macro. One that works with the current wireless Mac keyboard where the caps lock key does not stay down when pressed. I will make the changes you suggest and see what happens.
Oh!!! I think (but I'm not certain) that you are implying that you want the macro to trigger when the CAPS button is "green" but NOT depressed. But that's not how that trigger works. That trigger works when the key is pressed, not when the CAPS key is green.
If you want to detect when the CAPS key is green, you can't use a trigger for that, you have to use an IF statement. That is a condition. Like this:
Let me repeat, there is no trigger that detects when the CAPS key has a green light. You have to create your own code that tests if the key is green.
I found a solution that's a bit goofy but it will work for me. When the caps key is pressed to turn it off then I get both Caps Key Pressed and Caps Off spoken notifications.
Caps Lock Notification.kmmacros (7.0 KB)
If you are happy, that's all that matters, but your newest version still has the bug where it triggers multiple times. If you open the debugger and press CAPS (for more than a split second) you will see (and hear) multiple copies running. But if you tap CAPS quickly there may not be enough time for multiple copies to run.
That's not happening here -- not with the Caps Lock key, nor the Shift key, nor a naked A (for which the macro runs once but the A character is sent to the frontmost app multiple times.
Isn't "pressed" a one-shot (also allowing us a separate "released") while the repeater is "is down"?
Wow -- total fail on my part there! And that's after downloading and testing the original macros...
I've obviously hit the macro-writer's equivalent of walking into a room and then wondering why I went in there 
I still hold you in the absolute highest esteem. You have such a long history of being amazing that you could make 5 mistakes in a row and I would still hold you in the highest esteem.