I would really like to be able to saved out all the bar setup and layout information, kind of like ActionBarSaver does for the contents of the bar. I doubt I will be setting up too many more alts, but I have to go through the same painful process each time. I would like a command in BT rather than having to manually copy folders though since that may bring extra things along.
This sounds exactly what the Profiles part of the /bt window does: saves layout and options in a way that's available across all characters. Is there something there which doesn't do what you want?
Nothing needs to be "redone" for one spec of one class. Make sure one of your bars (typically bar 1) is toggled as the possession bar, with no freaky weird state configuration. My shadow priest did those quests with no troubles using the default BT configs.
I'm writing an addon that saves the current action-setup from the actionbar cuz i'm really tired spending about 10mins to replace all actions over and over again.
Action Bar Saver 2 works with minor fixes. (I know this, because I fixed it, and posted a patch to ABS2's page on wowinterface.) I think somebody may even be hosting a fixed version somewhere, but honestly haven't looked.
But before i go on with doing it quick and dirty i want to know if something like this is planned for the future?!
I would be surprised, just because that seems out of scope. Do one thing, do it well, etc.
4.4.11 up with showgrid fixed, keybinding conversion, and a fix for flyout buttons.
My firstborn child will be named Nevcairiel in your honor.
I should probably go look at the code before I ask this next question, but what the hey: is there a recommend way to programmatically toggle the showgrid for a given bar, or for all bars? What I have in mind is
1) normal play with showgrid off and buttonfacade set to 'zoomed'
2) run a /script that sets buttonfacade back to normal and showgrid to on
3) drag buttons around
4) run a /script to set things back to the way they are in (1)
That's the closest I think the current rules will allow for "show grid only while dragging buttons", which would be ideal for me. I've been playing all my toons with (1) for a long time and love it, but sometimes it's tricky dragging new spells into place when I can't see the empty grid. :-)
edit: er, forgot to mention a crucial bit: setting a buttonfacade to 'zoomed' hides the grid, which makes perfect sense, but that's the reason for the jumping through hoops in steps (2) and (4).
Actually in the 4.4.0-1 Alpha i already fixed the UpdateHotkeys taint.
I wish people would use alphas more when talking about issues =(
Your post here didn't mention "alpha", only 4.4.0-1. Curse client and the .toc file of what I have on disk both claim 4.4.0-1, so I concluded that I had the most recent release. As far as I can tell from looking at version strings, I still have the most recent release. When I toggled CC over to looking for alphas, it still claimed that BT4 is up to date, and as a bonus also no longer sees any disembedded library available for download *at all* for any other addon.
So perhaps I've wasted both your time and mine, but I don't see how I should have known any better. I think I'm about to give up on curse client and go back to downloading zip files by hand. I'm tired of it sending me down blind alleys.
I've grabbed the alpha .zip file directly and will try it out shortly, CC can go fark itself in the ear.
It's also hellishly depressing to read. Both in the sense of how fragile Blizzard has made their UI, and also in the sense of how sloppily so many addons are coded. Every time I look at a taintlog, I end up sending off half a dozen emails to authors of unrelated addons.
In BT4's case, I don't know how the taint is going to be avoided. Maybe I'm just not seeing a possibility. The log from running (almost) nothing but BT4 is attached; the relevant bits are the same as the log when running all my usual addons.
It starts when BT4/ActionButton.lua:355 replaces ActionButton_UpdateHotKeys. Can't use hooksecurefunc since it's a pre-, not a post-hook. Then when combat starts, UPDATE_BINDINGS fires, MultiCastActionButtonX:OnEvent() calls FrameXML/MultiCastActionBarFrame.lua:445's MultiCastActionButton_OnEvent(), which then calls FrameXML/ActionButton.lua:349's ActionButton_OnEvent(), which jumps down to line 382 to handle UPDATE_BINDINGS, and hits the now-tainted Action_Button_UpdateHotKeys.
I didn't know UPDATE_BINDINGS gets fired at the start of combat. Learn something new every day, I guess.
Edit: Ok i found out why. Tooltip Addons usually hook "GameTooltip_SetDefaultAnchor", and if they do that, they taint the MultiCastFlyout Code. Changing that hook to a secure hook will probably fix the issues caused by Tooltip addons.
Using 4.4.0, I get errors as soon as I enter combat, without dropping totems or even mousing over the totem bar:
[2009/08/17 23:40:43-4098-x1]: <event>ADDON_ACTION_BLOCKED:AddOn 'Bartender4' tried to call the protected function 'MultiCastActionButton5:Show()'.
<in C code>: in function `Show'
Interface\FrameXML\ActionButton.lua:192: in function <Interface\FrameXML\ActionButton.lua:163>:
<in C code>: in function `ActionButton_Update'
Interface\FrameXML\ActionButton.lua:366: in function <Interface\FrameXML\ActionButton.lua:349>:
<in C code>: in function `ActionButton_OnEvent'
Interface\FrameXML\MultiCastActionBarFrame.lua:445: in function `MultiCastActionButton_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
The only addon I could find that was (taintfully) messing with GameTooltip_SetDefaultAnchor was disabled before loading. I was getting the same error before disabling that addon. After the above error, testing issecurevariable("GameTooltip_SetDefaultAnchor") returned 1,nil (i.e., still secure).
I've never looked at the MultiCast* code. Not entirely sure where to even begin figuring out what could be causing this.
4.4.0 nolibs version isn't fetching LibWindow-1.1 or LibKeyBound-1.0 when grabbed via the curse client. All of the other nolibs library dependencies are installed, but not those two. I have no idea what might cause that.
Installing those two by hand restored everything to normal.