Differences

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

--- trigger:Typed_String [2023/09/13 08:07] – peternlewis
+++ trigger:Typed_String [2025/10/28 02:40] (current) – peternlewis
@@ Line 13: / Line 13: @@
 Keyboard Maestro will accept the trigger even if you use the delete key to correct it (for example, in the case above, if you typed "=en«delete»m=" the trigger will still fire. If you need to type the trigger text without the macro firing, type and delete a Shift-Space in the middle, like "=e«Shift-Space»«delete»m=".
-As above, typing Shift-Space will cancel the sequence, as will any control key or command key (eg Command-.), any macro execution, switching applications, clicking the mouse, or not typing for more than a few seconds. Tapping a modifier will not cancel the sequence, but will be considered part of the trigger string (v11.0+).
+As above, typing Shift-Space will cancel the sequence, as will any control key or command key (eg Command-.), any actively (Hot Key, USB Device Key) triggered macro execution, switching applications, clicking the mouse, or not typing for more than a few seconds. Tapping a modifier will not cancel the sequence, but will be considered part of the trigger string (v11.0+).
 You can optionally allow typed string triggers to work regardless of case, regardless of diacriticals.
@@ Line 27: / Line 27: @@
 If multiple typed string triggers match from the end (eg "hello" and "llo"), the longest will be used. If there are multiple matches with the same length (as can occur if you use the case or diacritic options), the conflict palette will be displayed, offering a selection of the matching macros. In this case, if all of the typed string triggers have the "Simulate N deletes before executing" option enabled, the deletes will be simulated immediately and then the conflict palette will be displayed; otherwise the deletes will not be simulated.
-Note that the system will not allow Keyboard Maestro Engine to see keys typed in its own windows (such as the [[action:Prompt for User Input]] or [[action:Custom HTML Prompt]]), so the Typed String triggers will not work within Keyboard Maestro Engine windows.
+Note that the system will not allow Keyboard Maestro Engine to see keys typed in its own windows (such as the [[action:Prompt for User Input]] or [[action:Custom HTML Prompt]]), so the Typed String triggers will not work within Keyboard Maestro Engine windows. Also note that Typed String triggers will not work well in the Keyboard Maestro editor itself as any change to the macros results in the macros being saved and resets the Typed String trigger buffer. So you will need to use a different trigger for working within the Keyboard Maestro Engine or editor.
 The system also will (rightly) not allow Keyboard Maestro to see keys typed in password fields, so Typed String triggers will not fire if you type them in most password fields. You can use Insert Text by Typing to type in to password fields (although this is a serious security concern, and there are some cases where it will not work properly), but you cannot use Typed String triggers while inside a password field.