You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a macro can run other macros, it can be helpful to define "utility" macros, not intended to be run on their own but instead to perform common macro steps that would otherwise be duplicated between various macros. It would be useful to have a way to prevent these utility macros from showing in the "Run a macro" box, to reduce visual clutter, and to prevent them accidentally being run individually.
I would suggest something like a prefix on the macro name, such as "_." or "hidden." or "util.", as this is easy to add into the settings without adding an extra layer of JSON hierarchy.
The text was updated successfully, but these errors were encountered:
It might be nice to have a way to define JavaScript functions that are accessible to all of the macros too since there could be a lot of repeated code there.
As a macro can run other macros, it can be helpful to define "utility" macros, not intended to be run on their own but instead to perform common macro steps that would otherwise be duplicated between various macros. It would be useful to have a way to prevent these utility macros from showing in the "Run a macro" box, to reduce visual clutter, and to prevent them accidentally being run individually.
I would suggest something like a prefix on the macro name, such as "_." or "hidden." or "util.", as this is easy to add into the settings without adding an extra layer of JSON hierarchy.
The text was updated successfully, but these errors were encountered: