Message: attempt to concatenate a boolean value
Time: 05/19/10 12:25:57
Count: 3
Stack: [C]: in function `strjoin'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:359: in function `GetSection'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:391: in function `DispatchItem'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:437: in function `UpdateButtons'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:218: in function `UpdateAllContent'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:153: in function `RegisterUpdateEvents'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:200: in function <Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:195>
[C]: in function `Show'
Interface\AddOns\AdiBags\AdiBags.lua:330: in function `Open'
Interface\AddOns\AdiBags\AdiBags.lua:493: in function <Interface\AddOns\AdiBags\AdiBags.lua:492>
(tail call): ?
[string "TOGGLEBACKPACK"]:1: in function <[string "TOGGLEBACKPACK"]:1>
When opening the bank or clicking the config button:
1x AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:502: attempt to compare two boolean values
<in C code>: in function `sort'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:548: in function `LayoutSections'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:219: in function `UpdateAllContent'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:153: in function `RegisterUpdateEvents'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:200: in function <AdiBags\widgets\ContainerFrame.lua:195>
<in C code>: in function `Show'
AdiBags-v1.0-beta-2-5-gb708a43\AdiBags.lua:330: in function `Open'
AdiBags-v1.0-beta-2-5-gb708a43\AdiBags.lua:529: in function `?'
CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
Locals:
(*temporary) = <table> {
1 = AdiBagsSection1 {}
2 = AdiBagsSection6 {}
3 = AdiBagsSection7 {}
4 = AdiBagsSection8 {}
5 = AdiBagsSection10 {}
6 = AdiBagsSection3 {}
7 = AdiBagsSection4 {}
8 = AdiBagsSection9 {}
9 = AdiBagsSection5 {}
10 = AdiBagsSection2 {}
}
(*temporary) = <function> @ AdiBags\widgets\ContainerFrame.lua:498:
(*temporary) = AdiBagsSection5 {
dirtyLayout = false
total = 1
0 = <userdata>
slots = <table> {}
width = 1
buttons = <table> {}
count = 1
name = true
category = true
height = 1
Header = <unnamed> {}
freeSlots = <table> {}
container = AdiBagsContainer1 {}
}
(*temporary) = AdiBagsSection5 {
dirtyLayout = false
total = 1
0 = <userdata>
slots = <table> {}
width = 1
buttons = <table> {}
count = 1
name = true
category = true
height = 1
Header = <unnamed> {}
freeSlots = <table> {}
container = AdiBagsContainer1 {}
}
---
Using Beta 2.5
Also a question regarding bag updating while they're closed. As a hunter, whenever i fire an arrow, the bag updates causing a slight spike in cpu usage (i used other bag addons in the past that had way higher spikes than i get with this though). Would it be possible to ''stop'' listening to bag updates whenever the bag window is closed (or the user is in combat)? Not a huge issue currently, but it's a suggestion.
This should be already the case, except maybe for the new item tracker. Try disabling it to see if it changes something. If it does, I'll add some code so that the new item tracker doesn't update until combat ends.
Since yesterdays alpha (posted by 7 raid time not at home to check version) I am seeing the same stacking problem. Before 36 mana pots would be 1 stack of 36 and 396 symbols of kings would be 396 in 1 stack. Now they are displayed as 20 + 16 mana pots and 300 + 96 SOK's. Other items as well but those are the 2 i remember.
The addon was working ok, but suddenly after I sent some mails, I got this error and started showing everytime I opened the bags:
Message: Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:502: attempt to compare two boolean values
Time: 05/20/10 00:20:40
Count: 2
Stack: Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:502: in function <Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:498>
[C]: in function `sort'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:548: in function `LayoutSections'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:219: in function `UpdateAllContent'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:153: in function `RegisterUpdateEvents'
Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:200: in function <Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:195>
[C]: in function `Show'
Interface\AddOns\AdiBags\AdiBags.lua:330: in function `Open'
Interface\AddOns\AdiBags\AdiBags.lua:493: in function <Interface\AddOns\AdiBags\AdiBags.lua:492>
(tail call): ?
[string "TOGGLEBACKPACK"]:1: in function <[string "TOGGLEBACKPACK"]:1>
Locals: a = AdiBagsSection6 {
dirtyLayout = false
total = 5
0 = <userdata>
slots =
Since yesterdays alpha (posted by 7 raid time not at home to check version) I am seeing the same stacking problem. Before 36 mana pots would be 1 stack of 36 and 396 symbols of kings would be 396 in 1 stack. Now they are displayed as 20 + 16 mana pots and 300 + 96 SOK's. Other items as well but those are the 2 i remember.
That's intentional. Incomplete stacks are shown separated by default. You can disabled this behavior by checking "incomplete stacks" in in virtual stack settings (with latest alpha).
@gi2k15: didn't have access to my computer today, I'm going to take a look.
Using v1.0-beta-2-7-g0940d3e, enUS locale - scale settings were still not saving. So I did a little investigating.
Issue: Scale slider does nothing. It will remember it's value within a session, but does not actually affect the scale, and forgets it's value after a reload. No entry in the SV file. It will scale if I use the mousewheel on the anchor, but still forgets the setting after a reload.
On line 286 of Options.lua there was a typo (addon.acnhorScale = value I assume should be addon.anchorScale = value). I fixed that, but it didn't help the issue. So I put a scale value into the SV file manually. After doing that the addon loaded at the right scale. Changing the scale via slider doesn't take affect until a reload. Changing it via wheel still works as expected. Scale now saves between reloads.
I'm still missing something, but hopefully that helps somehow!
ATM I'm working on these tasks :
- have a better interface to change manual filter,
- buy bang bag slot in the bank bag pannel.
Now, I'm also considering the following tasks/features:
- Adding a "advanced configuration" option, that would hide some of settings when unchecked. I would like suggestions about which options to hide.
- Adding a panel to change the section categories ordering (section categories are kind of hidden super-sections, used to group sections together in a given order),
- Drop an item anywhere in a bag to put it in a free slot,
- Right-click on a section while at bank to move all items of this section to the other side (same at mailbox to add items to a mail),
- Display some information in item tooltip when pressed a modifier key (like class, subclass and, max stack size and which filter put the item in that section),
- An option to enable "Lax section ordering", that would reduce wasted space by ignoring section ordering when need be.
Drop an item anywhere in a bag to put it in a free slot
I like this one a lot :).
An option to enable "Lax section ordering", that would reduce wasted space by ignoring section ordering when need be
I think Baggins does this if I'm understanding it right. Sometimes it's nice, sometimes it's a nuisance.
I would like an option to disable the fading of junk items while leaving the rest of the item highlights intact. Maybe a threshold option? Fading an item has other meanings in WoW and I keep seeing them and thinking my inventory is bugged!
I think Baggins does this if I'm understanding it right. Sometimes it's nice, sometimes it's a nuisance.
I eventually implemented it. The idea is the following: each section has a (hidden) category, that has a given (hidden ATM) order. All sections are then sorted by category order, category name, then section name. The option allows you to choose how these sections are layed out :
- by strictly following the order: this way the sections are always in the same, predictable order, no matter the number of items in each of them. This may wastes some space.
- by keeping sections of the same category together: category order is followed but the sections within a category may be reordered in an attempt to save some space.
- by filling item rows at most: order is totally ignored, the code tries to save the most space by building complete rows.
would it be possible to add an option to increase the height of the bank bag, currently with the settings I have my bank bag is wider than my screen (and I'm on a 30" monitor with 2560*1600 resolution)
thanks for the change, I'll do more test tonight and give you my results.
Using alpha version.
Using Beta 2.5
Also a question regarding bag updating while they're closed. As a hunter, whenever i fire an arrow, the bag updates causing a slight spike in cpu usage (i used other bag addons in the past that had way higher spikes than i get with this though). Would it be possible to ''stop'' listening to bag updates whenever the bag window is closed (or the user is in combat)? Not a huge issue currently, but it's a suggestion.
Reloading the UI resolved the problem though.
That's intentional. Incomplete stacks are shown separated by default. You can disabled this behavior by checking "incomplete stacks" in in virtual stack settings (with latest alpha).
@gi2k15: didn't have access to my computer today, I'm going to take a look.
Issue: Scale slider does nothing. It will remember it's value within a session, but does not actually affect the scale, and forgets it's value after a reload. No entry in the SV file. It will scale if I use the mousewheel on the anchor, but still forgets the setting after a reload.
On line 286 of Options.lua there was a typo (addon.acnhorScale = value I assume should be addon.anchorScale = value). I fixed that, but it didn't help the issue. So I put a scale value into the SV file manually. After doing that the addon loaded at the right scale. Changing the scale via slider doesn't take affect until a reload. Changing it via wheel still works as expected. Scale now saves between reloads.
I'm still missing something, but hopefully that helps somehow!
- have a better interface to change manual filter,
- buy bang bag slot in the bank bag pannel.
Now, I'm also considering the following tasks/features:
- Adding a "advanced configuration" option, that would hide some of settings when unchecked. I would like suggestions about which options to hide.
- Adding a panel to change the section categories ordering (section categories are kind of hidden super-sections, used to group sections together in a given order),
- Drop an item anywhere in a bag to put it in a free slot,
- Right-click on a section while at bank to move all items of this section to the other side (same at mailbox to add items to a mail),
- Display some information in item tooltip when pressed a modifier key (like class, subclass and, max stack size and which filter put the item in that section),
- An option to enable "Lax section ordering", that would reduce wasted space by ignoring section ordering when need be.
Any thought ?
I think Baggins does this if I'm understanding it right. Sometimes it's nice, sometimes it's a nuisance.
I would like an option to disable the fading of junk items while leaving the rest of the item highlights intact. Maybe a threshold option? Fading an item has other meanings in WoW and I keep seeing them and thinking my inventory is bugged!
I eventually implemented it. The idea is the following: each section has a (hidden) category, that has a given (hidden ATM) order. All sections are then sorted by category order, category name, then section name. The option allows you to choose how these sections are layed out :
- by strictly following the order: this way the sections are always in the same, predictable order, no matter the number of items in each of them. This may wastes some space.
- by keeping sections of the same category together: category order is followed but the sections within a category may be reordered in an attempt to save some space.
- by filling item rows at most: order is totally ignored, the code tries to save the most space by building complete rows.
Got the following though:
and
Hope this helps make a great bag mod even better :P
Started showing up out of nowhere, got quite a few of those.
Edit: Pops up whenever i open the bags now. Also noticed that there's an empty space between my Epic and normal white arrows in my bags.