Originally Posted by spiel2001
It's probably not going to work, initially, with macros because it has no way of knowing which spell ties to the target or not. It also requires that the button work with Blizzard's own "IsUsable()" logic. If Bliz can't determine whether or not the macro is currently usable on the current target, nUI won't be able to make the determination, either.
In order to support that sort of thing, I'm going to have to include the ability to specify what spells are associated with the button and that's not going to be able to happen until I get to the more advanced action bar code. Which, very likely, won't happen until after the 3.2 patch.
|
You just need to identify in the macro which spell you want it associated as and the engine should be able to do the rest.
Usualy the command #showtooltip is sufficient for you to set the macro designation.
For example on a lock you might do something like
#showtooltip Corruption
at the begining of the macro which then causes blizz api to recognize that macro as being the same as the corruption spell and will assign it the same attributes and tooltip as that spell including range coloring etc.