Hi, for the first time in ages im back to playing wow, but this time i am also building myself my own 100% custom interface... or so i thought i was, I have got an XP bar done that i am satisfied with, and I had some issues with the way i created action buttons and not having them show any cooldowns etc. So i decided to just move around with Blizzards buttons, however... things are not going as planned. I can easily get the buttons to where i want them to with ClearAllPoints() then move them to the spot i like with a new SetPoint(), but then things start to get complicated, I want only 5 Action Buttons visible at one time! It is essential for my clean look! So i use modifiers Shift, Control and Alt, and i can get the following effect just fine: See Attatchments 1-3,
HOWEVER.... now it becomes really strange when i do the same a 3rd time... this weirdoshizle happens:
See attatchments 1 and 4 The ActionButton1 through 5 has now hijacked the hotkeys alt Q through alt F! And the Buttons that were supposed to be different are nowhere to be seen.
Now there is no reason for this to happen but it doesnt matter which extra action bar i take the buttons from, when I overlap with the original bar a third time it always goes badly.
Im a bit lost to be honest what to do next with this thing, and was hoping some of you could help :)
Note that loop based or single run based methods result in the same things.
Also note this swapping wont work in combat, i presume i have to hook a method or two to override an actionbar lock.
Thanks for the tip, I have an idea of the issue rooted in stacking bars in Z that is in front of each other, will make them go to "page mode"
This gave me som differnet issues, as i could easily change page out of combat, the method ChangeActionBar(int); is restricted to NON-COMBAT calls.
However, through some digging at different sites the last couple of days, i came across a thread with someone trying to do the same thing. Unclear if he succeeded, but in this thread there was a reference to an old outdated AddOn from patch 5.2, called Paging, It turns out this addon once i updated it with the Current API variables and methods, works exactly like i want, even with my existing bits. There Answer is to look into the SecureHandlerTemplates, create a frame, and inherit from that template, then use a frame:SetAttribute("state-paging", SecureCmdOptionParse("[mod:alt]2")); if you whish to get to page 2 on presssing alt, and if its a while pressed you need to set the attribute again with "[mod:]1" this will return the page to page 1 if it isnt pressed. Its unclear to me at this point, but i suspect RegisterAttributeDriver(PagingFrame, "state-paging", "[mod:alt]2"); or what ever condition and action is the intended one must follow SetAttribute eachtime it has to be set.
I will update here once with full code and explanation once I figure it out, as i understand the struggle and frustration it can be to find someone who found the answer but didn't share it :).