I have a bug somewhat like few post back. When i hit buttons on keyboard when shift in any form other than caster (i'm druid) in fact buttons pressed on ActionBar1 (action bar of caster form). But when i click on buttons with mouse i works properly. What can be done to solve this problem?
P.S. I didn't change any settings of paging or keybindings
I tried the latest Dominos and it does seem to fix the 'buttons trigger action bar 2 instead of action bar 1' bug - it's certainly not recurred in 8K of honor's worth of BGs today :)
I seem to be misunderstanding something here tho - this started off as a 'lightweight' bar mod so I assumed it would shun it's own keymappings in favour of the stand Blizz ones (I seem to recall when Bartender did it's own mappings it went HORRIBLY wrong).
The fact that I have to rebind keys to make 'paged' bars work is a bit of a grind - 95%+ of users will have "1" thru "=" defaulted on their action bar and expect those keys to trigger the spells located within that bar whatever ACTUAL bar is paged into it - either by Shift-2,3,4,5,6,7 or 'Stealth' or 'Shadowform' or whatever.
That's basically how bars should work - at least IMO
If I have to map diff keys to diff bars I don't need to page that bar in to hit the key for it!!!
edit: I actually got the stock action buttons working with state changes, but I also broke right click selfcast doing so. Gonna work on it more when I get home today.
Looks like its either "right click selfcast" or "bindings working by default"
I'm going to go with right click selfcast.
What blizzard sortof needs to do is modify the SecureActionButton_OnClick(button, "LeftButton") call in ActionButtonUp to not use that Leftbutton arg, and instead use GetModifiedAttribute, or something.
Do you notice any discernible difference in performance with redrange enabled versus when its disabled?
Basically, every time a frame is rendered, RedRange asks each visible action button:
* Is it time to check my status again?
* Should I be red or not?
* Is this a change from last time?
If all of those conditions are true, then the action button's redness is updated. Otherwise, RedRange does nothing.
Now, the blizzard CPU profiler sees that check and says, "hey this addon is doing something, I better record its time" So it then increment's red range's CPU count. Now, what I suspect happens here is that, even though its a very very tiny amount of CPU work being done, the CPU profiler can only insert a value greater than say 0.05, and nothing lower than that. So the redrange addon may just be doing 0.00001 work, but is counted as 0.05. and thus you see the inflated number for CPU usage.
It is within my ability to write a more efficient version, but unless red range is really killing someone's FPS, I do not think there's a need to.
There *IS* out of range indication in Dominos. It uses the same method as the default UI. If you want/need more than that, there is RedRange. RedRange is a perfectly good addon, written by a perfectly good author. If you have a problem with RedRange, let Iriel know and he'll fix it. (Yes, the same Iriel that's a featured artist on wowinterface and a friendly green poster/dinosaur on the wow forums.)
I didn't say there wasn't out-of-range indication in Dominos. My point was that since it's directly related to action bars and how they're displayed, in my opinion it falls under the purview of Dominos as an action bar mod.
But like you say, RedRange works. And Tuller is free to do what he likes. I was merely expressing my preference on the off chance he feels like accommodating that preference. ;)