I got two feature I think would be nice.
1. Be able to shift-left link in to the search box.
2. Don't show stacks one row per stack but instead show the total of the item you search for and then in the result have a column showing how many stacks it is.

other then that, this was the right addon I needed when I have mailed stuff to my alts in panic and now try to find everything again...


I can't reset the filters and/or clear the window.
And if you could add so that you can browse with the mouse-wheel in the window, that would be nice...

Very interesting, detailed analysis.

Only thing with the conclusion is that I am not running a slow computer here. Not the latest, but not slow, either. 3 Ghz, 1GB of RAM, fully updated Windows XP, the latest video, sound & network drivers (I'm vigilant in keeping those updated as I know what I'm doing with computers), DSL, 105-125 ms median latency, no background processes whatsoever using up CPU or disk read/writes, 45 FPS median frame rate. Never have a problem with lag here, unless its caused server-side.

I left the thing up for a full 30 minutes or so during one of the testing trials before killing it; it remained frozen throughout that time. So its really is in effect a complete freeze rather than a big slow down.

Will give this another go when another WoW patch comes up.

I was having the exact same lockup problems as described below after deleting my cache(wbd) folder. Upon logging in my 1st time after a cache clear, I will lockup checking my mailbox. Simple solution I had was to disable simplebankstate, login & check my mailbox, than reenable simplebankstate & all is kosher I figured it was related to rebuilding the cache of my mailbox items & simplebank was trying to check the items b4 they got cached. Im far from a programmer to help in a solution but if u try deleting your cache folder, that should reproduce the error.

This problem still exist with 1.2.21 btw

The problem only occurs under a very specific (but common) circumstance. And only occurs within a limited time frame. So its hard to replicate unless you are within the same time frame.

As in:

--Exit WoW before an official WoW patch that increases the version number (such as 2.0.4 to 2.0.5). have SimpleBankState active at the time you last exited WoW.

--Come back into WoW after the patch.

--Open a mailbox on any character on a single account after a patch (with SimpleBankState still enabled). Within 2-10 seconds, WoW locks up. The mailbox inventory list doesn't completely finalize showing. As in you will see "Alliance Auction House" or "Unknown" in the mail headers but the item icon doesn't appear before the lockup/screen freeze happens.

--Kill WoW, come back in (after rebooting if needed and/or doing a disc scan to repair files corrupted by having to reboot before all apps could be closed), try a different character on the same account. WoW locks up again as above.

--Kill WoW, come back on the first character tried. Still locks up.

--Disable SimpleBankState after logging out and log back in. Open a mailbox on one of the characters in which it locked up previously. The problem goes away.

--Reenable SimpleBankState after successfully logging on as above. It does not cause lockups any more. Only on the mailbox openings on an account right after a patch with it enabled.

Thanks for the useless fanboi comment, its appreciated .

As the end result is the same, what major difference does the testing criteria make? Whether or not its an interaction with another mod (I already listed the only mail/inventory mod I had running, which was Postal), it is this mod that was determined to be the cause of the crash.

Sure, it may be slightly easier to debug if you know that for sure its not an interaction with another mod helping to cause the problem. But there is only so much program crashing and file corruption that a person will put up with trying to find the cause of a problem before saying "no more". Lucky I tested as much as I did to find the cause.

Irregardless of whether its "hard for an author to fix" or not, it shouldn't have been allowed to have happen in the first place. Other inventory mods don't have this problem currently. But one that did cause lockups when opening a mailbox after a patch (before it was fixed a few patches ago) was MaterialsTracker.

So its not a problem unique to this mod. And more than one person has experienced it. It happens only in specific circumstances. And seeing as the cause was this mod (whether alone or in combination with other mods being run) and the problem was WoW crashing, yes, it is unacceptable.

Have fun.

A better test would probably have been to just enable this mod and nothing else and then see if you could reproduce the crash. And since it seem this isnt a universal problem i would say that youre statment that it is unacceptable is pretty far off from the truth. The simple truth is that problems like this can be hard to reproduce for an author and even more hard to fix.

SimpleBankState (SBS) v1.2.8 here (the latest on any UI site) freezes/crashes WoW opening a mailbox on an existing character immediately after a WoW patch (2.0.5 the latest). Same behavior as with earlier versions (as mentioned by a poster on Curse called "ainfigree" at this link on Nov 24/06).

This has happened during WoW 2.0.4 here too with an earlier SBS version. But I was not as methodical in my testing as I was this time to make sure SBS was the guilty party.

After coming back from the opening of my mailbox that caused WoW to freeze/crash in WoW 2.0.5, I disabled inventory & mailbox mods one at a time until the culprit was found. To make sure it was SimpleBankState (after several WoW crashes/freezes), I enabled everything I had going when the crash first happened, then disabled just this mod. It is for sure this mod.

A terrible bug; SimpleBankState really should not still be available for release as it is. Depending on whether you are fullscreen or windowed when the crash/freeze caused by SimpleBankState happens, you may have to reboot, causing a forced close & loss of open data in all apps on your desktop. Or else kill WoW alone (if you are able to) losing all saved variables data. And so on. Doing this has the real potential of causing file errors on your hard disk as well.

Unacceptable behavior for a released mod.

I get this message when I try and sort the items.

Could this be fixed asap, please?

And great addon btw, simple and very user friendly.... if I could get the sorting to work. I mean the leftclick sorting btw, not the filtering because that is working as intended (i.e. very nicely).

I love this mod. Thanks for update