Following up on your own post is bad form but too bad. Hopefully this post will help some others avoid the same over-engineering path I went down...
So I was attempting to implement Aragent's per-class/spec 2 step macro solution over the week-end and discovered - as Lax has mentioned - that Wow helper macros without key bindings are silently dropped from the ISBoxer addon per-character files.
As I'm trying to set this up for all possible class/spec combinations (saves adding to it later) and I don't want to consume 30 unique key bindings, I broke the macro helpers into 30 separate units (one per class/spec) with a Rotation and a Proc macro in each. I then created 30 ATGs (plus the appropriate level ATGs) and altered my spam key steps to invoke the appropriate helper action for each class/spec. For those of you doing the math, that means 30 actions in each of step 1 & 2.
A conversation with Lax on irc this morning about my concerns about the performance of that many actions in a single step, led to Lax chiding my about a lack of virtualization, which led to the recognition that I had made things way too complicated.
Specifically, the 30 class/spec ATGs and the 30 actions per step are both unnecessary. If you use the same key strokes for the Rotation and Proc macros (e.g. use Ctrl+[ & Ctrl+] for Roation & Proc respectively) in each class/spec helper, you don't need to assign characters to class ATGs and you can remove that part of Aragent's macros (as I noted above), although you do still need the level ATGs. You then assign the helper sections on a per character basis, which both acts as a selector and ensures that ISBoxer will protect you from sticking the same character in multiple groups as the assigned key sequences will clash. The spam macro them becomes very simple: just invoke the key presses directly (e.g. use Ctrl+[ & Ctrl+]). No named macro assignments, no ATGs.
tl'dr: Moral of the story: Keep It Simple Stupid
Connect With Us