Differences

This shows you the differences between two versions of the page.

--- Frequently_Asked_Questions [2024/12/28 03:48] – [Is Keyboard Maestro compatible with Sonoma?] peternlewis
+++ Frequently_Asked_Questions [2025/10/03 09:53] (current) – peternlewis
@@ Line 1: / Line 1: @@
-{{INLINETOC 3-4}}
+~~INTOC~~
 ==== How do I get started? ====
@@ Line 49: / Line 49: @@
 Yes, Keyboard Maestro version 11 is fully compatible with Mojave. In fact, Keyboard Maestro versions going back as far as version 2.x still work fine on Mojave.
-Mojave has bugs with its Accessibility System Preferences which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again.  Generally this is only required once when upgrading to Mojave. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
+Mojave has bugs with its Accessibility System Settings which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again.  Generally this is only required once when upgrading to Mojave. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
 Note that Mojave adds some nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 57: / Line 57: @@
 Yes, Keyboard Maestro version 11 is fully compatible with Catalina. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Catalina. Versions of Keyboard Maestro prior to version 4.0 will no longer run on Catalina due to it dropping support for 32-bit applications.
-Catalina continues with the bugs with its Accessibility System Preferences introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
+Catalina continues with the bugs with its Accessibility System Settings introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
 Note that Mojave and later add lots of nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 65: / Line 65: @@
 Yes, Keyboard Maestro version 11 is fully compatible with Big Sur. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Big Sur.
-Big Sur continues with the bugs with its Accessibility System Preferences introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
+Big Sur continues with the bugs with its Accessibility System Settings introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
 Note that Mojave and later add lots of nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 73: / Line 73: @@
 Yes, Keyboard Maestro version 11 is fully compatible with Monterey. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Monterey.
-Monterey continues with the bugs with its Accessibility System Preferences introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
+Monterey continues with the bugs with its Accessibility System Settings introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
 Note that Mojave and later add lots of nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 81: / Line 81: @@
 Yes, Keyboard Maestro version 11 is fully compatible with Ventura. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Ventura.
-Ventura continues with the bugs with its Accessibility System Preferences introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
+Ventura continues with the bugs with its Accessibility System Settings introduced in Mojave which may require toggling the Accessibility permissions of Keyboard Maestro Engine off and on again, and/or deleting the Keyboard Maestro Engine preference from the Accessibility system and having it re-added.  Generally this is only required once when upgrading to Catalina. See the [[assistance:Accessibility_Permission_Problem|Accessibility Permission Problem assistance]] for more information.
 Note that Mojave and later add lots of nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 93: / Line 93: @@
 Also, Sonoma restricts access to the wireless information unless you grant the application Location security permissions, but unfortunately Apple do not request those security permissions when the API is used, and there is no way to manually add Location permissions. In Keyboard Maestro version 11 you can poke the system to request this permission by executing the [[action:Get_Location|Get Location]] action once. Hopefully Apple will resolve this in upcoming versions of Sonoma.
-Sonoma may continue with the bugs with its Accessibility System Preferences introduced in Mojave - we will see as more people use Sonoma.
+Sonoma may continue with the bugs with its Accessibility System Settings introduced in Mojave - we will see as more people use Sonoma.
 Note that Mojave and later add lots of nagging for security permissions that can be tedious when first using Keyboard Maestro or when first controlling a specific facility or application.
@@ Line 106: / Line 106: @@
 Also, Sequoia tends to re-request Screen Monitoring permissions periodically which may be a nuisance, and for headless or unattended Macs may be a serious problem.
+==== Is Keyboard Maestro compatible with Tahoe? ====
+Yes, Keyboard Maestro version 11 is fully compatible with Tahoe. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Tahoe.
+Tahoe seems to have some sort of bug with where it places status menus, so they may move around or have gaps between them. Hopefully Apple will resolve the issue promptly.
+The Tesseract OCR library that Keyboard Maestro uses frequently fails with a memory corruption in Sequoia, and likely in Tahoe too (unverified). It is unlikely we will be able to fix this, however the Apple Text Recognition supported by recent versions of Keyboard Maestro generally works better in most cases. Note that it currently supports English-only, so if you use OCR on non-English text, this may be a problem for you.
+Similar to previous versions it is likely there are endless little niggles in the security system which may cause issues when first getting Keyboard Maestro permission.
+Also, Tahoe tends to re-request Screen Monitoring permissions periodically which may be a nuisance, and for headless or unattended Macs may be a serious problem.
@@ Line 268: / Line 280: @@
 ==== Can I use the Fn key as a modifier? ====
-Basically, no. The Fn key is not a modifier, it is a hardware toggle that toggles whether the physical key behaves as a function key (eg F3) or a hardware key (eg increase brightness).  Its behaviour can be toggle in the System Preferences, Keyboard preferences.  You can use a function key as a trigger as long as it is behaving as a function key (that is either with or without the Fn key depending on your system preference setting).  But the Fn key does not affect the hot key per se, it changes whether the key on the keyboard acts as a function key (needful for hot keys) or a hardware key (which cannot be used with a hot key).
+Basically, no. The Fn key is not a modifier, it is a hardware toggle that toggles whether the physical key behaves as a function key (eg F3) or a hardware key (eg increase brightness).  Its behaviour can be toggle in the System Settings, Keyboard preferences.  You can use a function key as a trigger as long as it is behaving as a function key (that is either with or without the Fn key depending on your system preference setting).  But the Fn key does not affect the hot key per se, it changes whether the key on the keyboard acts as a function key (needful for hot keys) or a hardware key (which cannot be used with a hot key).
 Think of your keyboard as have two rows of keys, one row of function keys and one row of hardware keys - the Fn key toggles which row is “visible”.
@@ Line 324: / Line 336: @@
 ==== How can I select Status Menus? ====
-Selecting status menu items is difficult primarily because there is no easy way of specifying them - they don't have names so its hard to identify them.
+Selecting status menu items (sometimes known as menu bar items) is difficult primarily because there is no easy way of specifying them - they don't have names so it is hard to identify them.
-You can use a Click at Found Image, although even that can be difficult as they often animate or change icons based on various states.  If the icon does not animate or change state (or has a known state when you want to select from it), then this can be a good solution, followed by Insert Text by Typing "Menu Name%Return%"
+You can use a [[action:Move_or_Click_Mouse|Click at Found Image]], although even that can be difficult as they often animate or change icons based on various states.  If the icon does not animate or change state (or has a known state when you want to select from it), then this can be a good solution, clicking to open the menu and then followed by [[action:Insert_Text_by_Typing|Insert Text by Typing]] "Menu Name%Return%"
 To click relative to an image, you use the Mouse Click action, configure it to be relative to a found image, and take a screenshot of the desired area of the screen using Command-Control-Shift-4, and paste it into the image well on the action.  The image has to be unique (which includes not being visible in the action if the image is small enough not to be shrunk in the image well) otherwise Keyboard Maestro will not know where to click.  The Display option in the action will allow you to see where Keyboard Maestro is matching.
+You may also be able to use AppleScript to click the menu bar, something like:
+```
+tell application "System Events" to tell process "Adguard"
+	click menu bar item 1 of menu bar 2
+end tell
+```
 ==== How should I name my variables? ====
@@ Line 352: / Line 371: @@
 You can learn more about regular expressions in various places:
-* The BBEdit or TextWrangler Help has extensive documentation on regular expressions.
+* The BBEdit Help has extensive documentation on regular expressions.
 * gskinner’s [RegExr](http://gskinner.com/RegExr/) provides a live testing field for regular expressions (requires Flash).
 * [Beginning Regular Expressions](http://www.amazon.com/Beginning-Regular-Expressions-Programmer/dp/0764574892/ref=sr_1_1?s=books&ie=UTF8&qid=1339154441&sr=1-1) book.
 * [Mastering Regular Expressions ](http://www.amazon.com/Mastering-Regular-Expressions-Jeffrey-Friedl/dp/0596528124/ref=sr_1_2?s=books&ie=UTF8&qid=1339154441&sr=1-2) book.
 * [Regular Expressions Tutorial](http://www.regular-expressions.info/tutorial.html) online resource.
+* [Regular Expression 101](https://regex101.com) online regex tester (but note that it has different settings and different flags so just because a regex works there does not mean it will work the same in Keyboard Maestro).
 ==== How can I close the Keyboard Maestro editor window? ====
-You can (v8+) click the close box on the editor window and it will quit the editor for you.
+You can click the close box on the editor window and it will close the editor window.
+If the last window is closed, the editor will quit. The Keyboard Maestro Engine will continue running and processing your macros after you quit the Keyboard Maestro editor. Read the [Quick Start](http://wiki.keyboardmaestro.com/Quick_Start) for more details about the difference between the editor and the engine.
+Note that while you can have more than one editor window open, it can quickly slow down Keyboard Maestro so it is generally best to only have one editor window open unless you need to refer to two macros at the same time. Also, it is generally a good idea to quit the Keyboard Maestro editor when you are not editing your macros and leave just the Keyboard Maestro Engine running.
-The Keyboard Maestro Engine will continue running and processing your macros after you quit the Keyboard Maestro editor. Read the [Quick Start](http://wiki.keyboardmaestro.com/Quick_Start) for more details about the difference between the editor and the engine.
 ==== What does Keyboard Maestro use the Contacts for? ====