Overview: When editing a macro, the FrontBrowserJavaScript token continues to evaluate regardless of whether the action that contains it is disabled or if Evaluate Condition Results (in the View menu) is off. The only way to stop the evaluation is to stop editing the macro. Steps to Reproduce Ad…

Are you proposing a change to the KM Editor's behaviour? I can see why the current behaviour is undesirable for you, and I can see you have some workaround ideas, but what would you consider to be the ideal behaviour for the KM Editor? Do you think perhaps there should be a new menu item on each ac…

While the manual page for Tokens correctly states that "Tokens in Keyboard Maestro represent placeholders, that you enter during design time, for information that will be replaced in the text at run time", it does not state whether KM will keep polling for that information. On the face of it, there …

[image] kevinb: whether KM will keep polling for that information The following discussion sheds a (dim) light on this: [image] Odd Behaviour of AppleScript Dictionary When KM Token in Use Questions & Suggestions This is really a post/question for @peternlewis ... T…

[image] Airy: Are you proposing a change to the KM Editor's behaviour? Yes. [image] Airy: but what would you consider to be the ideal behaviour for the KM Editor? There should be some way to stop the repeated evaluation while editing a macro that has an action that contains this token…

[image] ar-km: [image] Airy: Do you think perhaps there should be a new menu item on each actions cogwheel to override the global evaluation flag? That might be a solution. Agreed. That would be one way to do it. Although that still runs into the issue I mentioned where it might be very …

[image] Airy: As I said, I was proposing that the flag be added to "all actions", not just the actions that "could possible accept the token." Ah. Sorry about the misunderstanding. I guess that would do it too :slight_smile: Some items in the cog menu seem to be available for all actions. B…

[image] ar-km: This is why I didn't consider suggesting it as a globally available option. Fair enough. I was simply suggesting a universal toggle because it seemed like the simplest quick fix. There may be other approaches. For example, there could be a new tab in the KM Editor Configuration…

[image] Airy: For example, there could be a new tab in the KM Editor Configuration that would list all 200 tokens (or just a few of them that really need this feature), each with a checkbox to allow users to disable that specific token from being evaluated in the editor. That's an interesting…

[image] ar-km: The only way around this, while editing, is to delete the action containing the FrontBrowserJavaScript token. If you undisclosed the action, it will not be evaluated (since there is nothing to display). While editing it, you could add a “typo” to the token (eg XFrontBrowserJa…

[image] peternlewis: If you undisclosed the action, it will not be evaluated (since there is nothing to display). While editing it, you could add a “typo” to the token (eg XFrontBrowserJavaScript). Ah! These both work. I like un-disclosing the best. Thanks.

[Bug and/or Feature Request] `FrontBrowserJavaScript` token evaluates constantly and can't be disabled while editing

Questions & Suggestions

tiffle June 21, 2024, 11:01am 4

The following discussion sheds a (dim) light on this:

[Bug and/or Feature Request] `FrontBrowserJavaScript` token evaluates constantly and can't be disabled while editing

Options