disable macro(this macro)

[Jacob L]

Having the ability to disable this macro, would mean that cloning macros would not break them and require me to refactor them.

 

[FrameXX]

Can you explain more what you mean?
You can immitate disabling macro by making boolean variable and set all macro to work only if that variable is true. Than just add set variable false action.

 

[Jacob L]

under the enable/disable macro action, you should be able to turn off the [this macro] so that it can just be carried to other cloned macros

 

[KeeperCake]

Can you explain more what you mean?
You can immitate disabling macro by making boolean variable and set all macro to work only if that variable is true. Than just add set variable false action.

Think I get it.

Many actions involving other macros have the option to select "this macro" instead. The macro will perform the action on itself instead of another.

I just tried a test. Presently, you have to configure which macro to disable/enable manually and change accordingly after copying or cloning.

Say you name a macro "Test" and save it.

	Name: Test	Notes
Trigger	Empty
Action	Empty	Empty macro because you have to save and reopen for editing.

You can reopen it for editing, add the action to disable a macro, and select "Test" from your list of macros. Your macro will disable itself when it gets to that action.

	Name: Test	Notes: same macro after editing
Trigger	Empty
Action	Disable Macro, "Test"	Since the macro had been saved, we could now add the action and select "Test" from a list.

You could then clone the macro. The name of the clone will default to "Test 2." Running "Test 2" will still disable "Test." To make "Test 2" self-disabling, you'd have to edit it and reconfigure the disable action.

	Name: Test 2	Notes: clone of "Test," not same macro
Trigger	Empty
Action	Disable Macro, "Test"	By default, this clone disables the original macro. Have to reconfigure manually if you want a self-disabling clone.

Jacob is suggesting that "this macro" be added as an option when you're selecting a macro for the disable/enable action. Then copying and cloning will automatically apply the action to whatever macro it's in, not the one it came from.