![]() ![]() The only solution I have found is to manually go through every macro and manually re-select the specified application. When this problem happens, it seems to happen with every macro, and every command. This works as expected - except sometimes it forgets which application I have specified, and brings up a different application instead. I will look for a workaround, but currently I don’t know of an alternative.I keep having this recurring problem where keyboard maestro is losing track of which applications I have specified in the macro.įor example, I have a simple macro where hitting Command-2 will bring a specific application to the front. Unfortunately, Apple has removed the CGSession tool that is used to lock the screen and return to the Login Window. Interestingly, on a fresh install of Big Sur, current screen saver works and returns a valid screen saver, so my guess is that this is some sort of update issue where the preference is no set correctly (although changing the Screen Saver preference does not resolve the issue). ![]() In Mojave and later, the AppleScript command to retrieve the current screen saver may return screen saver "", which is invalid, in which case the Keyboard Maestro action, which is essentially tell application "System Events" to start current screen saver This has been reported as a bug to Apple. Window positions of Alerts and Prompt For User Input windowsĪs described ( BUG - Input Window Shifts Downward in v9.1 on Big Sur - #10 by peternlewis), Alerts and Prompt For User Input will move vertically each time they are opened in Big Sur. If you can change the target hot key to something other than an arrow or function key, then Keyboard Maestro can trigger it based on simulating the key. Whether this is a bug or a “feature” is unknown. Simulating Function/Arrow keys does not trigger other application hot keysĬatalina and Big Sur do not support triggering hot keys with simulated keys for function keys or arrow keys, but weirdly does allow it for other keys. This is rather infuriating, as the checkboxes clearly show permission, so anyone would assume that means they have permission, but the system is actually lying, and you have to toggle the checkboxes off and on again to grant permission - who would even think to try that? This has remained a bug through Mojave and Catalina and now also confirmed in Big Sur. ![]() This especially happens if you already have Keyboard Maestro and upgrade the system. If you have any troubles with accessibility (eg typing keystrokes, selecting menus, copy/paste, etc), you need to toggle the accessibility permissions (System Preferences, Security & Privacy, Privacy, Accessibility) for Keyboard Maestro and Keyboard Maestro Engine off and then on again. You will have to ensure you enable Accessibility for both Keyboard Maestro and Keyboard Maestro Engine. PI Engineering are looking in to the issue, and hopefully so is Apple. There appears to be an incompatibility between Big Sur and XKey devices such that the "value" component of their key events is no longer 1-4 bytes (holding a number), but is inexplicably 32 bytes. XKey Devices do not work with Keyboard Maestro in Big Sur However, Mojave and Catalina have two accessibility settings bugs which can cause problems trying to enable accessibility permissions for Keyboard Maestro and Keyboard Maestro Engine (which is required fo…Īs they are confirmed to still exist in Big Sur, I'll copy them below here. So lets make this clear - Keyboard Maestro itself has no known problems with Catalina or Mojave. UPDATED: noted that there are still people having troubles with Catalina and its accessibility issues. TIP: Resolving Catalina/Mojave Accessibility/Security Permissions Issues Tips & TutorialsĬatalina (and Mojave really) Accessibility and Security Permissions ![]()
0 Comments
Leave a Reply. |