Bug with disabled macros?

[FlameInYourSide]

If a macro is disabled, why can it still be called from other macros?

using version 2.2.0.11

[Gintaras]

It disables only trigger that is set in Properties. Also if using command line. In code, can be used this:

int iid=qmitem("macro name")
if(!dis(iid)) mac iid ;;run the macro if not disabled

[FlameInYourSide]

Just for testing purposes, sometimes I just want to quickly disable and re-enable a macro.

I found instead, however, a quick renaming of the macro I don't want to run is a lot easier than your proposal.

Thanks.

[ken gray]

also put in 'end' on the first line :wink:

[FlameInYourSide]

Can you give an example of what you mean by 'end' on first line?

[ken gray]

Code:

Copy      Help

end
_s.getclip
_s.findreplace("[]" "htnshtn")
_s.from(_s "htnshtns;")
out _s

[Gintaras]

If the macro is launched using mac, or a trigger, or Run button, ie not called as function, you can also use " /" in the first line.

--

When you rename the macro, you should get error with mac. Don't know what method you use to launch the macro.