Tell application "Finder" to set visible of process "Keyboard Maestro" to false Tell application "Keyboard Maestro" to activate set myKMVar to "true"ĭo shell script "pkill 'Keyboard Maestro'" This is the result I came up with to get everything going as I needed it to. This is the short path I have the most hope for, though if we can figure out the performance issue as a longer term discussion then it would be great as well… If we can initially try to resolve this by looking at how AppleScript can get feedback from keyboard maestro to know when to execute its next step, this would be useful. It seems like some kind of open CL process that gets backgrounded can loop on top of itself or something like that, but who can say… ![]() The latest updates have helped with battery consumption in the background a lot, but not with reduced display performance when running a loop for a long period of time as described. These are central to want I’m doing and I’ve long had issues with battery consumption and Keyboard Maestro if its left running in the background, even if the macro is not running anymore. I have a suspicion it has to do with image recognition and GPU functions in keyboard maestro. so running Keyboard Maestro for a long time alone will not allow me to replicate the issue. Additionally, the issue does not occur unless Keyboard Maestro is executing a loop for a long time. Display performance is already terrible in safe mode anyway, so its pretty hard to tell. Thanks for the suggestion JMichaelTX, but I cannot test my macros in safe mode because they require Ableton Live to be open which cannot function in safe mode. Tell application "Keyboard Maestro Engine" Tell application “Finder” to set visible of process “Keyboard Maestro” to false Tell application “Keyboard Maestro” to activate I have not made the loop yet, because I don’t think there’s any point until I figure out how to get keyboard maestro to tell AppleScript that its done its thing.ĭo shell script "pkill ‘Keyboard Maestro’" This is what my apple script function looks like so far. At that point I want to kill the Keyboard Maestro Application before I repeat everything all over again. Problem is I’m not able to know when Keyboard Maestro finished the macro. So the workaround I’m working on is to run keyboard maestro and then a macro from apple script (applescript is the host here), when its done then kill keyboard maestro, and repeat. I’ve had this issue on 4 different Macbook pros at this point. Although I’ve provided screen capture evidence of this via support, its still a persistent issue. The only workaround I know of is to close the Keyboard Maestro Engine process and reopen it again, and then my display performance is great again. After it runs for a around a day or more it can really slow down the UI/graphics performance of my Mac immensely.Įventually, this means that the keyboard maestro macro itself will fail when expecting to click somewhere and miss its opportunity to do what its supposed to do. ![]() I have had a problem with keyboard maestro ever since I started using it, about 4-5 years now. This is going to be somewhat of a strange question and situation to communicate.
0 Comments
Leave a Reply. |