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 Next revision Both sides next revision | ||
|
Frequently_Asked_Questions [2017/09/19 09:52] peternlewis [What is the difference between text token fields and calculation fields?] |
Frequently_Asked_Questions [2017/11/23 05:03] peternlewis [What is the upgrade price?] |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| * If you purchased Keyboard Maestro directly after March 1 2017 you have received a free upgrade to Keyboard Maestro 8. | * If you purchased Keyboard Maestro directly after March 1 2017 you have received a free upgrade to Keyboard Maestro 8. | ||
| - | * If you purchased Keyboard Maestro 7, you can upgrade for $18 until 19 November 2017. | + | * If you own any previous version of Keyboard Maestro, you can upgrade for $25. |
| - | * If you own any version of Keyboard Maestro, you can upgrade for $25. | + | |
| * If you purchased Keyboard Maestro from the Mac App Store, you can convert your license to a direct license, and then you can upgrade for $25. | * If you purchased Keyboard Maestro from the Mac App Store, you can convert your license to a direct license, and then you can upgrade for $25. | ||
| * Otherwise you can purchase a new version for $36. | * Otherwise you can purchase a new version for $36. | ||
| Line 289: | Line 288: | ||
| Which brings us to the point of this article: *naming best practices*. | Which brings us to the point of this article: *naming best practices*. | ||
| + | |||
| + | In version 8, variables that start with "Local " 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. | ||
| 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. From a Shell or AppleScript'ers point of view these don't look “natural”. | 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. From a Shell or AppleScript'ers point of view these don't look “natural”. | ||
| Line 337: | Line 338: | ||
| ==== How can I close the Keyboard Maestro editor window? ==== | ==== How can I close the Keyboard Maestro editor window? ==== | ||
| - | The Keyboard Maestro editor is designed to be run only when needed, and then quit. By not allowing the main window to be closed, the application encourages you to quit it instead. I could go with the metaphor of quitting the application when you close the window, but I've never liked that behaviour. | + | The Keyboard Maestro editor is designed to be run only when needed, and then quit. By not allowing the main window to be closed, the application encourages you to quit it instead. |
| + | |||
| + | In Keyboard Maestro 8, you can click the close box on the editor window and it will quit the editor for you. | ||
| 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. | 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. | ||
| Line 351: | Line 354: | ||
| If possible, you should avoid using mouse click actions. They tend to be very fragile, easily broken by subtle changes to the system or applications. And they also require the screen to be in the expected state, so you usually need to add a Pause action before them to ensure the item they are clicking on is where it is expected to be. | If possible, you should avoid using mouse click actions. They tend to be very fragile, easily broken by subtle changes to the system or applications. And they also require the screen to be in the expected state, so you usually need to add a Pause action before them to ensure the item they are clicking on is where it is expected to be. | ||
| - | That said, there are two easy ways to get the screen coordinates for a mouse click. | + | That said, there are two easy ways to get the screen coordinates for a mouse click. |
| The first is to simply record the click. Turn on recording in Keyboard Maestro, go to where you want to be, wait a could seconds for the screen to be stabilised so the click will be relative to the front window, and click. Turn off recording, delete any extraneously recorded actions and you have your coordinates. | The first is to simply record the click. Turn on recording in Keyboard Maestro, go to where you want to be, wait a could seconds for the screen to be stabilised so the click will be relative to the front window, and click. Turn off recording, delete any extraneously recorded actions and you have your coordinates. | ||
Frequently_Asked_Questions.txt · Last modified: 2023/12/30 23:32 by peternlewis
Page Tools
