will this addon be updated for 4.0? thanks

I just checked 4 similar addons on Broker CPU, and this is what I found.

CPU usage
1. TullaRange 0.37-0.47%
2. RangeColors 0.71 - 1.31%
3. ButtonRange 2.92 - 4.35%
4. RedRange 3.35 - 4.75%

TullaRange came in as least CPU usage, but RangeColors also checks/colors spells you have too little mana(blue) to use.

It there a command to open this up in wow to configure it? Or is it a install and go or in my case not go. There is nothing in the readme files about this. I've tried /redrange, /rr, /show redrange and /show rr.

And additional to this to avoid wasted code cycles HasAction should be used. Which RedRange does not use. So some code is executed that need not be.

In short if this was to be used >
1. Code cycles would become more efficient.

HasAction(actionSlot) - Flag
* 1, if the slot contains an action
* nil, if the slot is empty

Wonderful how flags work =)

I also have lag with this mod. I've had to change to Buttonrange.

http://www.wowinterface.com/download...ttonrange.html

I have this issue as well. seems to be having difficulties with abilities that require certain variables. In my case things like dancing rune weapon, death pact, icebound fortitude, and anti-magic shield will black out. But when the required runic power is available they light back up. I know this is working as intended in a way but the degree to which they darken is to the point of making the icons for the given abilities look like they are empty buttons.

I hope this mod will get the appropriate update but if you are like me and having blacked out buttons hurts your OCDs then i recommend installing another mod I found on WowInterface in the meantime. Buttonrange.

Regarding OnUpdate, wowwiki has a code snippet that might help you:

http://www.wowwiki.com/Using_OnUpdate_correctly

It's because the Addon HAS to listen to the "ActionButton_OnUpdate" event, which is unfortunatley fired every frame. I don't know why, ask Blizzard.

In city e.g. on dummy you have ~60 FPS, but on raid 25man boss fight you normally have ~20 max (k with i7 you should have more), funny thing is: as you have lower FPS, there are also fewer "onUpdates", so CPU usage of this addon goes down in low FPS fights, so it's somewhat okish.

I will see if one can "throttle" the updates to somethin like "10 times a second".

As a tip right now: don't use multibar addons with this one, try to minimize the number of action buttons on screen to the bare minimum. With a normal action bar (10 icons) i don't have heavy CPU usage..

On the other hand, most CPU profiling addons show a percentage of the addons CPU usage across ALL addons, so when you see "RedRange 90%" it DOESN't mean RedRange is using 90% of CPU ressources. It means, redRange is using 90% of all CPU ressoruces the addons as a whole use, and that doesn't have to mean much. If it's the only addon registering for an "On_Update" event of some sorts, it most likely will show up "high".
For me (Core 2 Duo) RedRange only uses 5%, if using CPU heyva addons like DoTimer (don't!), and now after some better selection of addons, it's up at 12% of the share.

Afaik, there is no measurement to see how much %of CPU an addon uses, but I could be wrong.

this addon with the lastest version of 3.1.1 when used with Dominos, is causing Dominos to have blank spell icons in your action bars.

you spell is still there but you can't see the icon which makes it really hard.

I was waiting for this to be updated and then found ActionButtonColors which does the same thing and has been updated to work with 3.1. It seems to only be available on curse though at:

http://wow.curse.com/downloads/wow-a...tails/abc.aspx

This addon works in 3.1, however, it is a CPU hog; it eats up a lot of your CPU.

I use all three and I am not having an issues but more then willing to help with the troubleshooting.

This problem is happening as well with me. However I have pin pointed it down do buttonficade. With dominos and buttonficade on, redrange causes buttons to disappear. Reload sometimes makes them appear sometimes not. Shutting off red range corrects the problem of course, but so does turning off button ficade.