Hey Guys,
----------------------------------------------------------------
# Auth: Christopher Stone
# dCre: 2018/04/20 09:54
# dMod: 2018/04/20 09:55
# Appl: Keyboard Maestro Engine
# Task: Quit and restart the Keyboard Maestro Engine
# Libs: None
# Osax: None
# Tags: @Applescript, @Script, @Quit, @Restart, @Keyboard_Maestro_Engine, @Engine
----------------------------------------------------------------
tell application id "com.stairways.keyboardmaestro.engine"
if running then
quit
else
launch
end if
end tell
----------------------------------------------------------------
This sort of thing is a good reason to have FastScripts on your system – even the free version which has unlimited menu scripts and 10 available keyboard shortcuts. (For $9.95 U.S. you get unlimited global and app-specific keyboard shortcuts.)
I currently have 25 AppleScripts that drive the Keyboard Maestro Editor in various ways, and they're all in FastScripts – because I don't want Keyboard Maestro driving itself – particularly since its dead in the water when the engine isn't running.
I need a number of my scripts to work when the KM Engine is not running,
There are many other advantages.
- Testing AppleScripts using a different run mechanism.
- Offloading long-running processes that reduce performance of the other app.
- More I can't think of pour le moment.
I'm still using it alongside Keyboard Maestro 15 years after I bought it, because there's synergy having both – and that lets me get more work done.
I feel the same way about Typinator. Although Keyboard Maestro will do most of what Typinator will do (albeit a little more awkwardly), Keyboard Maestro can't do text-expansions in its own running UI Actions – Typinator can – and vice versa.
Once again there's good synergy between the two utilities.
-Chris