If you want to create custom flyouts, you can use FlyoutButtonCustom in conjunction with BT4 (and several other action bar addons, and the default action bars).
I am unable to collapse my quest helper winder on screen when bartender is active for only one of my toons. Any reason why that may be?
Most likely you have an (empty) action bar occupying the same area on the screen as the collapse button. Type /bt4, unlock your bars, and look for green rectangles. If you're not using those bars, find them in the options (eg. "Bar 4") and uncheck the "Enable" box. If you're only using part of the bar, and don't want to move it, you can change the number of buttons so the bar area is smaller (eg. if you only 4 of the 10 buttons on the bar, just set it to only have 4 buttons, so it only takes up 4 buttons worth of screen space).
You can also use the game's /framestack command to explore which frames are underneath the mouse cursor; this will be helpful if it's not actually a Bartender bar.
If neither of those help, make sure you have "Display Lua Errors" turned on under Interface Options > Help. It's possible an addon (maybe Bartender, maybe something else) is actually breaking the quest window; if there's an error message, it should give more information about the problem.
BT4 doesn't save any keybindings itself, it just uses the game's standard keybinding system. However, there are addons that will let you save keybinding profiles and swap between them. The first one that came up in a search was Binder but there are others if you want to look for them.
If there is an easy way to identify if another addon is interfering with this functionality, please let me know how and I will do my best to check/verify this myself.
You'd have to use the custom visbility states and play with macro conditionals, then. For example, if you want Bar 1 to page through the standard 6 pages, and Bar 2 to only flip between two pages that are not any of those 6 pages, you could use something like this on Bar 2:
[page:1/3/5] 7; [page:2/4/6] 8
This means that when the "active page" is 1, 3 or 5 that bar will show page 7; when it's 2, 4 or 6 it will show page 8. However, there's still no way to make paging only affect one bar -- when you change the "active page" it affects all bars.
Enabling paging for a bar doesn't give that bar its own unique set of pages -- it makes the bar react to "/swapactionbar" and "/changeactionbar" commands, including those issued by your "next/previous action bar" key binds. If you enable paging on 3 bars and then "/changeactionbar 5", all 3 of those bars will then display page 5. Blizzard's terminology is a little misleading. "/changeactionbar" etc. don't do anything with bars in the sense that everyone uses the term -- they actually act on pages.
Since Bartender uses the Blizzard action ID system, you are limited to 120 action IDs across 10 action pages. You could get creative with macro conditionals to make paging work on multiple bars (eg. one bar that cycles through pages 1, 2 and 3, and another bar that cycles through pages 4, 5 and 6) but in general having multiple paging bars is not well-supported by the game's API -- the "next/previous action bar" keybinds will only cycle through pages 1-6 and ignore 7-10 since those are (in the default UI) reserved for use in specific stances, and all commands that change action pages will affect all bars with paging activated, so in the above example, when you went from page 1 to page 2 on your first bar, your second bar would also go from page 4 to page 5 -- so it's best just to stick to only one manually-paged bar.
And to clarify, it's not actually copying the contents of Page 9 to Page 1 -- it's just showing you Page 9 instead of showing your Page 1 while you're in Bear Form.
If you really want to see Page 1 in Bear Form, you can change this behavior on the "State Configuration" tab in the options for the specific BT4 bar (probably Bar 1) -- but be warned, if you put bear abilities on Page 1, then shift out of Bear Form, you'll still have bear abilities on Page 1 that you can't use, making the whole bar basically useless. You should keep using Page 1 for abilities you want to use in your regular humanoid form.
May we ask to break the inexplicable archaic traditions and do us some innovation as a Xmas Gift 2014 and include a very simple numeric cooldown to Bartender so we don't have to install the 125th standalone addon for such a tiny feature. Franky, it should be a pretty basic and default part of any action bar. Everyone needs it.
Yes, and therefore "everyone" should either use OmniCC, or use the new option in the default UI to show numbers instead of graphics for cooldowns.
Why should every action bar author reinvent the wheel and duplicate this code in their addon, when you can just install OmniCC if you want this feature? Other than the negligible overhead of reading a few additional files from disk during the loading sequence, if you want 10 features, there is no real difference between running 7 addons that each provide 1 or 2 features, and running 1 addon that provides all 10 features. In fact, for most users, the latter will be less efficient since they are now running extra code for features they don't want.
Even if Bartender4 included cooldown numbers for its own buttons, users would still have to install OmniCC to get a good numeric cooldown display on the rest of the buttons in the UI, which would completely defeat the point.
This is pretty much the same explanation for why I don't duplicate Clique in Grid, and it applies equally here. :p
In the options for each bar there's a "Show Grid" checkbox -- make sure it's unchecked. If you still see the backgrounds after turning off that option, then they're being added by whatever addon you're using to skin the buttons, rather than by Bartender itself.
Just so I can test : Anyone know a way to easily do the possess/vehicle thing?
The daily dragon quest on the middle level of the dragon tower (I don't remember offhand what it's actually called) in Dragonblight is good for this. Just remember to not turn in the quest until you're done testing. :p
Whenever I enter a vehicle, I get the action bar you should get, ... However, when I then try to use [the keys bound to] those action buttons, nothing happens. They only work when I manually click on the buttons.
Skip steps 2-4. If you get to the end and still have the same problem, attach your BT4 saved variables file (see step 7) to a post so someone can look at it.
Next time it happens, type "/fstack" and see what's listed. It sounds like some addon is creating an invisible frame over the entire screen (assuming mouse buttons "don't work" over the entire screen) that's catching mouse events. This doesn't really sound like something BT4 can cause, though, and I certainly haven't ever had any such problem. ???
Based on a quick look through LibActionButton-1.0 I'd guess you need to register for a callback:
function MyAddon:OnButtonContentsChanged(button, state, kind, value)
-- button - reference to the button object
-- state - string, corresponds to button:GetAttribute("state")
-- kind - string, eg. action, spell, empty
-- value - action ID, spell ID, etc.
end
local LAB = LibStub("LibActionButton-1.0")
LAB.RegisterCallback(MyAddon, "OnButtonContentsChanged")
You should be able to get the binding for a button using:
button:GetHotkey()
You may also want to register for the "OnKeybindingChanged" callback which passes a reference to the button and the new key binding.
While it might not be relevant in your particular case, BT4's saved variables are account-wide, not per-character, so they aren't stored under the server folder, they're in the top-level SavedVariables folder:
World of Warcraft > WTF > 123456#1 > SavedVariables > Bartender4.lua
Open the normal Key Bindings window, scroll down to the Action Bar section (not the BT4 section), and bind the desired keys to the "Previous Action Bar" and "Next Action Bar" functions.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Most likely you have an (empty) action bar occupying the same area on the screen as the collapse button. Type /bt4, unlock your bars, and look for green rectangles. If you're not using those bars, find them in the options (eg. "Bar 4") and uncheck the "Enable" box. If you're only using part of the bar, and don't want to move it, you can change the number of buttons so the bar area is smaller (eg. if you only 4 of the 10 buttons on the bar, just set it to only have 4 buttons, so it only takes up 4 buttons worth of screen space).
You can also use the game's /framestack command to explore which frames are underneath the mouse cursor; this will be helpful if it's not actually a Bartender bar.
If neither of those help, make sure you have "Display Lua Errors" turned on under Interface Options > Help. It's possible an addon (maybe Bartender, maybe something else) is actually breaking the quest window; if there's an error message, it should give more information about the problem.
http://phanx.net/addons/help#conflicts
[page:1/3/5] 7; [page:2/4/6] 8
This means that when the "active page" is 1, 3 or 5 that bar will show page 7; when it's 2, 4 or 6 it will show page 8. However, there's still no way to make paging only affect one bar -- when you change the "active page" it affects all bars.
Since Bartender uses the Blizzard action ID system, you are limited to 120 action IDs across 10 action pages. You could get creative with macro conditionals to make paging work on multiple bars (eg. one bar that cycles through pages 1, 2 and 3, and another bar that cycles through pages 4, 5 and 6) but in general having multiple paging bars is not well-supported by the game's API -- the "next/previous action bar" keybinds will only cycle through pages 1-6 and ignore 7-10 since those are (in the default UI) reserved for use in specific stances, and all commands that change action pages will affect all bars with paging activated, so in the above example, when you went from page 1 to page 2 on your first bar, your second bar would also go from page 4 to page 5 -- so it's best just to stick to only one manually-paged bar.
If you really want to see Page 1 in Bear Form, you can change this behavior on the "State Configuration" tab in the options for the specific BT4 bar (probably Bar 1) -- but be warned, if you put bear abilities on Page 1, then shift out of Bear Form, you'll still have bear abilities on Page 1 that you can't use, making the whole bar basically useless. You should keep using Page 1 for abilities you want to use in your regular humanoid form.
Yes, and therefore "everyone" should either use OmniCC, or use the new option in the default UI to show numbers instead of graphics for cooldowns.
Why should every action bar author reinvent the wheel and duplicate this code in their addon, when you can just install OmniCC if you want this feature? Other than the negligible overhead of reading a few additional files from disk during the loading sequence, if you want 10 features, there is no real difference between running 7 addons that each provide 1 or 2 features, and running 1 addon that provides all 10 features. In fact, for most users, the latter will be less efficient since they are now running extra code for features they don't want.
Even if Bartender4 included cooldown numbers for its own buttons, users would still have to install OmniCC to get a good numeric cooldown display on the rest of the buttons in the UI, which would completely defeat the point.
This is pretty much the same explanation for why I don't duplicate Clique in Grid, and it applies equally here. :p
The daily dragon quest on the middle level of the dragon tower (I don't remember offhand what it's actually called) in Dragonblight is good for this. Just remember to not turn in the quest until you're done testing. :p
http://phanx.net/addons/help
Skip steps 2-4. If you get to the end and still have the same problem, attach your BT4 saved variables file (see step 7) to a post so someone can look at it.
function MyAddon:OnButtonContentsChanged(button, state, kind, value) -- button - reference to the button object -- state - string, corresponds to button:GetAttribute("state") -- kind - string, eg. action, spell, empty -- value - action ID, spell ID, etc. end local LAB = LibStub("LibActionButton-1.0") LAB.RegisterCallback(MyAddon, "OnButtonContentsChanged")You should be able to get the binding for a button using:
You may also want to register for the "OnKeybindingChanged" callback which passes a reference to the button and the new key binding.
While it might not be relevant in your particular case, BT4's saved variables are account-wide, not per-character, so they aren't stored under the server folder, they're in the top-level SavedVariables folder:
World of Warcraft > WTF > 123456#1 > SavedVariables > Bartender4.lua