WowAce

Well, it looks like I'm orders of magnitude worse at thinking I replied when I didn't. >.>

Insanity in optimizing something to death may be my natural state. I should probably spend more time working on config screens or something!

Very many addons do this already, but I was having so much fun writing it that I couldn't stop, even when I kept finding out about more range-coloring addons I hadn't heard of.

I like mine the most but I'm biased. :P It does profile very well though!

Some other things I tried that didn't work, but might be interesting.

I tried hooking :SetVertexColor on the red buttons, so they'd memorize the attempted color change, but turn it immediately back to red. This worked, and had the trick that hooksecurefunc put the hook in the object instead of the prototype, so I could nil it to unhook it later. It didn't scale well to handling OOM colors though, because that meant hooking all the buttons not just the few red ones.

I tried using :GetVertexColor instead of IsActionUsable, because the Bliz code had just set the color to be consistent with IsActionUsable. I thought this was very clever ... but it turns out the two functions have similar overhead, so there was no point.

Oh I have something I wrote up about that, and was waiting for approval before I posted the first comment. I worked on this for 5 days before I found out about tullaRange, and was somewhat disappointed since I saw you had the same main innovation of one big timer instead of N little timers. At that point I'd put too much into it to throw away though. This was a reaction to ButtonRange instead of RedRange, but I guess the two are similar enough that the result is also similar.

The main differences I see are that I replaced the flashing logic, and I have oor > oom in priority, because I treat out-of-range as its own flag that's separate from is-usable.

I'm not quite sure what to do with this. It does profile better than tullaRange, but tullaRange performs well enough that I wouldn't've written something just to try improving on it. I was trying to make something run better than ButtonRange.

I'm also sort of annoyed at how much the Blizzard code spams updates on ACTIONBAR_UPDATE_USABLE. I may try unregistered the buttons for it and handling it myself, but at that point I have to consider how much I'm replacing the buttons instead of working with them; at that point maybe what I want is just to use a bar mod that replaces everything.