User Tools
Frequently_Asked_Questions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
Frequently_Asked_Questions [2024/12/26 23:17] peternlewis [How should I name my variables?] |
Frequently_Asked_Questions [2024/12/27 22:48] (current) peternlewis [Is Keyboard Maestro compatible with Sonoma?] |
||
|---|---|---|---|
| Line 96: | Line 96: | ||
| 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. | 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. | ||
| + | |||
| + | ==== Is Keyboard Maestro compatible with Sequoia? ==== | ||
| + | |||
| + | Yes, Keyboard Maestro version 11 is fully compatible with Sequoia. In fact, Keyboard Maestro versions going back as far as version 4.x still work fine on Sequoia. | ||
| + | |||
| + | The Tesseract OCR library that Keyboard Maestro uses frequently fails with a memory corruption in Sequoia. 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 there are endless little niggles in the security system which may cause issues when first getting Keyboard Maestro permission. | ||
| + | |||
| + | 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. | ||
| + | |||
| ==== Reporting a bug ==== | ==== Reporting a bug ==== | ||
| Line 329: | Line 340: | ||
| Which brings us to the point of this article: *naming best practices*. | Which brings us to the point of this article: *naming best practices*. | ||
| - | Variables that start with "Local " (v8+) will be local to the macro in question, and that start with "Instance " will be local to the macro instance (ie, that macro and all the macros that it executes). Consider availing yourself of these local variables if appropriate. | + | Variables that start with "Local" (v8+) will be local to the macro in question, and that start with "Instance" will be local to the macro instance (ie, that macro and all the macros that it executes). Consider availing yourself of these local variables when appropriate. |
| - | Other variables are global and so can be used between different macros and retain their values over time allowing you to store information for later use. | + | Other variables are global and so can be used between different macros and retain their values over time, thus allowing you to store information for later use. |
| Keyboard Maestro variables can have whitespace characters in their name. This is good for human readability. It also makes for better user experience in User Input dialogs. Whitespace characters are converted to underscores in scripts. | Keyboard Maestro variables can have whitespace characters in their name. This is good for human readability. It also makes for better user experience in User Input dialogs. Whitespace characters are converted to underscores in scripts. | ||
Frequently_Asked_Questions.1735273054.txt.gz ยท Last modified: 2024/12/26 23:17 by peternlewis
Page Tools
