bBars 

okay...been doing some testing...since I'm thinking of using this bar mod as a replacement for the bulky "Bartender" mod and I've found that the only positioning problem seems to be with "bMultiBar1". The others seem to save position correctly, even when attached to "bMultiBar1" at least relatively. I'm thinking it's a problem with loading in referencing some assumed base point for "bMultiBar1"...still running through the code and testing...more when I know more

edit: I take it back...it's not just "bMultiBar1" but all bars that are not attached to "parent" bars. "child" bars layout correctly, but the parent bars seem to "snap" to corners, top/bottom, or center based on proximity prior to reload.

edit2: seems that on loading variables "3" and "4" for setpoint are not being either read or applied (or both obviously)... (anyone ever notice I love QA'ing others code?)

edit3: **FIXED**
Hope that helps...and now I'm can officially state that I LOVE this bar mod...and it's replaced Bartender4 for me completely! Great work!

A new favorite, small memory footprint, easy to configure, no cluttered interface/configuration.
Uses the default binds, so you can easily disable the addon and keep all your keybinds.

A new favorite.

Could we please get ractionbutton support also?

It doesn't work on the button borders and I'd rather not have to use Masque/Buttonfacade

Love the addon! but Is there any way to hide the minimap button?

I'm having trouble with the keybinding. No matter how I keybind (if i use Blizzards keybind options, or the "/bbars bind" command), there's something wrong between bMultiBar1 and bMultiBar2.

I don't really understand what's going on, because it seems my bMultiBar2 has 12 buttons as it should, but they are called bMultiBar2button13 to bMultiBar2button24. Why aren't they 1-12 instead?

Anyway, the bug i wanted to report is this; Let's say I bind the first button on the first actionbar to "Q". That's ActionButton1 on bMultiBar1. The problem is that that keybind gets copied and applied to the first button on the second actionbar too, bMultiBar2button13. I think there's something wierd going on here.

I've tried clearing all my keybinds, even deleting my keybind-cache in the WTF folders, tried with no other addons enabled, and this still happens. Any clue on what's going on? Other than that, I must say I love your addons. They are so simple and yet strong, GREAT work!

Edit: And yes, it's vice-versa. If I bind a button on bMultiBar2, that gets copied to bMultiBar1 aswell. It happens both ways.

So loaded it and set it up, ..however now when you loging it only gives LUA errors and becomes disabled.

Message: Interface\AddOns\bBars\bBars.lua:38: attempt to call global 'LibStub' (a nil value)
Time: 07/03/12 15:34:50
Count: 1
Stack: Interface\AddOns\bBars\bBars.lua:38: in main chunk

Locals: bBars = bBars {
0 = <userdata>
config = false
frames = <table> {
}
default_positions = <table> {
}
}
addonName = "bBars"
ns = <table> {
}
LBFGroup = nil
(*temporary) = nil
(*temporary) = "LibButtonFacade"
(*temporary) = true
(*temporary) = "attempt to call global 'LibStub' (a nil value)"

for some reason, bars 1 and 2 are mirrors of each other.. any way to page switch one of them?

edit: in bartender4, bar2 is different than bar2 in bbars, I've tried shift-mousewheel pageswitching from to switch main action bar(out of config mode) , but can't get access to my bar2 while running bbars (in MoP beta). Also, when i'm in a vehicle, the bar doesn't change to vehicle controls...

Nope, can confirm, its still trying to access barsDB ( a nil value) and will not fire ; ;

if i add the bbars part to the addons file i'll get an lua-crit-message .. how can i bring this addon to worK?