Bagnon 

I haven't updated Bagnon since 1.7.3, as ver2 didn't appeal to me, now 3.3 is out and have to use it.

Every time I hide ammo bag or keyring, the rest of the bags keeps shifting downwards and I have to keep moving it.
Also theres no options to lock bags and bank bag seperatly.

True, and there's not much you can do about it other than to move the frame farther down or up the screen. Basically, Bagnon anchors itself to the corner its closest to to handle proper repositioning when you rescale/adjust your resolution/etc.

Yes, but if you lock all frames, you can still move them via holding down alt.

I am having a problem, I have not updated this addon for months and months but had to today due to patch.

I used to be able to stop a bag showing in bagnon window and have it open in standard blizzard bag image but now it just opens all the bags except the ones I deselected ???

If you know what im refering to can you help please.

Edit
Nvm, dunce moment and found the option lol. Searching for ages earlier and it wasnt til I posted this I found it lol. Always the bloody way eh.

Need!

hey just letting you know, i love this addon. But the only thing i dont really like is how you have to have to have four addon folders to download this whole thing. can't you put them all in one folder?

like many others i had been using an old version of bagnon, i tried updating it a few weeks ago before the patch and i noticed lag every time i opened up my bags so i deleted it from my interface folder and reinstalled the old version which was lag free

when the patch hit the old version no longer worked so i downloaded the latest version and the lag is back

has anyone figured out how to get rid of the half-second screen freeze each time bags are opened?

edit: the old version i was using was 1.4.7 if that helps

Bagnon_Config is its own folder because its load on demand. That means that it only uses memory if you actually decide to change a configuration setting.

Bagnon_Forever is its own folder because other addons exist for tracking inventory information, like Altoholic and the Armory addon. In addition, I use it for Combuctor.

Bagnon_Tooltips is its own folder for no good reason at this point in time :P It should be merged into Bagnon_Forever.

I think I still need to do some profiling to improve performance. Bagnon 2.0 is new code, after all.

Why don't you add an option to set the anchor to what you want?

Not sure if this is a Bagnon bug but when i am in combat i can't reorg by bags.

i am primarily healer and sometimes when the battle just doesn't require my full attention i like to sort by bags (not interested in combuctor, not when i organize it left side sell right side auctionhouse, pots on top, quest on bottom)

however i have noticed in 3.3 that i can't drag items around my bag.
i can move stuff around on my action bars in combat (if that matters), but not in bagnon

I seem to be able to do that in combat. Do you get the issue with all other addons disabled?

Its on my issue tracker now.

Can the bags and bank have frame names like "Bagnon_Bank" or something along those lines? Seems that the names are assigned on their first creation, so if I don't open my bags first, the frame names are reversed.

This makes creating a decent looking KGPanel kind of tough.

They will in the next version:
Inventory -> BagnonFrameinventory
Bank -> BagnonFramebank
Keyring -> BagnonFramekeys
GuildBank -> BagnonFrameguildbank

Hello,

I have updated to the latest version of Bagnon and Combuctor. Each time I visit a vendor, AH, guild bank and my back I get this error mesg.

80x Bagnon-2.12.3\components\frameSettings.lua:21: table index is nil

Then I have to reload my UI in order clear the error. When that error happens. My inventoy no longer sits in the frame and when I close it, my inventory does not show up. Please let me know if you need additional information.

These are the other errors I get after trying to reopen my bags

1x Combuctor-2.2.2\itemFrame.lua:120: attempt to call method 'Highlight' (a nil value)
(tail call): ?:
Combuctor-2.2.2\itemFrame.lua:185: in function `Regenerate'
Combuctor-2.2.2\itemFrame.lua:44: in function <Combuctor\itemFrame.lua:42>
<in C code>: in function `Show'
Interface\FrameXML\UIParent.lua:1967: in function `ShowUIPanel':
Combuctor-2.2.2\frame.lua:651: in function `ShowFrame'
Combuctor-2.2.2\frame.lua:645: in function `ToggleFrame'
Combuctor-2.2.2\Combuctor.lua:250: in function `Toggle'
Combuctor-2.2.2\Combuctor.lua:183: in function `ToggleBackpack'
Broker_Bags-v1.4-Release\Broker_Bags.lua:35: in function <Broker_Bags\Broker_Bags.lua:34>
<in C code>: ?
DockingStation-0.3.3 (Beta)\Core.lua:120: in function `pcall'
DockingStation-0.3.3 (Beta)\Plugins.lua:292: in function <DockingStation\Plugins.lua:288>

Locals:
(*temporary) = "LeftButton"
(*temporary) = false
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = <function> defined =[C]:-1

I have to stop the automatic display for now on Bagnon.
Pst One thing i notice is that when i took out thoe check to autoload my bags when I go to a vendor, it did it any way with no errors. Hope that helps

In a logical sense it can be made to facilitate. In short if largest bag space is x apply to all slots. Then apply x (max slots) - y (current slot). And define that say for example the current bag is 4 slots short of max. It can then hide them based on this conditional. And then a global setup for all characters can indeed be made.

[ ] [ ] [ ] [ ] [x] -- character 1 bag 1
[ ] [ ] [x] [x] [x] -- character 2 bag 1

With this a global layout can be applied to both character bag 1 spaces. It would just hide the unavailable slots and scale the layout appropriate to its settings.

And frankly its something I have wanted from this add-on for a while. And do hope this suggestion is used. Or spurs a better idea of use. May be some work but many of your users have wanted this feature. And I am one of them. So hoping you reconsider your stance to not wanting to do it.

Are you using Bagnon + Combuctor at the same time? If so, don't (they're incompatible with each other).

@Sieben11:
I'm not really sure I understand your system.