|
Well I have come to terms with said weirdness, but I'm pretty sure it was much worse when I first tried it in beta.
I have this one macro, which is bound directly to a key using an addon setting an override binding. (relevance of the latter unknown) I press this key, macro is not executed and I get the popup. I click OK and get an error stating that SetAllowDangerousScripts was tainted by a different addon. Without doing anything else, I press the same key again to execute the macro, again macro is not executed and popup.. pops up. I click OK again, but no error this time. Again I don't do anything else and press the macro key a third time. This time the macro is executed without any errors or warnings.
Not sure how that works!
__________________
Grab your sword and fight the Horde!
|