Something went wrong during the renaming of your button. I added a check for the nil case to r75664 If you still have an issue in that version then if you can come up with an exact recipe to reproduce it that would be kool. Something like:
I wasn't renaming any buttons, just removing them from the bar.
I got the following error after removing multiple buttons from the Basic bar. I was using the Rock config interface and had buttons selected in the tree pane and was click the Remove button in the right panel for each one. After removing a few, I ended up with multiple Water buttons further along the bar which showed as blank areas in the actual bar itself and this error occurred when I tried to select one of the Water buttons in the config.
[2008/05/31 14:51:02-4441-x2]: AutoBar-2.04.02.54 beta.75501\AutoBarClassButton.lua:796: attempt to get length of local 'sortedItems' (a nil value)
Only items that return true for the IsUsable() and IsConsumable() API functions shuffle at the moment. Cooldown will also be checked for them so you can use shuffle on a mixed stone / potion / other cooldown list. I will add zone checks if its necessary.
That's very cool, I'm looking forward to that.
The reason I ask about zone checks is because of items like Bottled Nethergon Energy (http://www.wowhead.com/?item=32902) which is only usable in the Tempest Keep instances and so I would prefer to use those before Mana Potion Injectors or Super Mana Potions. Unfortunately, I think they probably return true from IsUsable() and just give an error message in the error frame when you try to use it outside of Tempest Keep.
The shuffle work is coming along nicely. It currently shuffles single item types all the way to nothing left. I still have to deal with rescanning for stuff that was added after combat started. Tomorrow I will work on swapping in the next best item at which point the first release of it can happen.
Is the shuffle going to consider whether items are usable in the current zone? And shuffle by cooldown remaining?
I believe that Bongos 3 support is either there or will be there soon, and Bartender 4 supports it. There are a couple of users attempting to get in touch with the author of ItemRack to add support, and will hopefully have something in the near future.
There is a Wowace addon called Bongos3_ButtonFacade which adds ButtonFacade support to Bongos3.
Just after repositioning bar after it had been docked (inadvertently while dragging around) to the chat window.
[2008/04/26 11:36:48-4215-x2]: AutoBar-2.04.01.46 beta.71514\AutoBarClassBar.lua:611: attempt to index global 'barPositionDBList' (a nil value)
Error re-occurs after every reload/login now, I'll have to zap the saved variables.
Could you add an option to completely disable all docking? My UI is completely non-standard and when dragging a bar around it docks to seemingly invisible things and it's rather annoying trying to get it positioned correctly.
Removing a button from a bar only works until the next reload/login when the button reappars at the end of the bar. This happened for the Hearth, Trinket 1 & 2, Mount, Potion Cooldown: Health, Stone Cooldown: Rejuvenation, Track buttons.
Turning off bar lock (so the bars are green) and then unchecking Enable from the right-click menu on my Paladin class bar seems to have no effect. With bar lock on, disabling the bar from the waterfall menu seems to work correctly.
Also with bar lock off, right-clicking a button does not configure it as the tooltip suggests, but actually uses the item. Luckily I experimented with a trinket :P
Why dont you post the very first bug you get? It is the only one that matters...
I did. The one I quoted in my original message is the first error that occurs. The stacktrace is somewhat confusing though since it doesn't pinpoint an addon as the cause of the problem, it's almost as if LSM3 is the originator, but that's impossible since I do NOT have LSM3 installed as standalone library. I double-triple-checked that.
Believe me, if I could pinpoint another addon as the culprit from the stacktrace, I would. But the only evidence I have to go on is that all hell breaks loose and about 10 of my Wowace mods blow up when AutoBar is enabled.
This has nothing to do with AutoBar. What you need to do is quit wow and run wau. Then start wow again. This will not only get the missing library CallbackHandler-1.0 by updating LibSharedMedia-3.0, it will allow Wow to notice its presence as it starts up.
Let's say this does not work. Then please on the left side of your wau (Wow Ace Updater) prefs the ONLY things you should have checked are:
"Default mode WITH externals"
If that was not the case then make it so and update again.
Next, lets imagine that whatever mod you use, and it is not AutoBar, because AutoBar uses neither LibSharedMedia-3.0, nor CallbackHandler-1.0, was checked in incorrectly and does not have the lib added correctly. Well you are just going to have to go out and get yourself a copy of CallbackHandler-1.0 and manually add it to your mods as a standalone library until such time as the mod author sees fit to fix their stuff.
I don't run disembedded libraries. I agree with you that it's stupid and the embedded libraries are a much better way to do things. Nor do I use WAU. I switched to WUU a week or two ago. I made sure that it's settings were to update WITH externals. I had also just updated all my Wowace mods, including AutoBar. I know not to update them piecemeal precisely because of the problem of mismatching/out-of-synch libraries.
CallbackHandler-1.0 appears multiple times in different mods, some of which are enabled for this particular char, so it must be available to load.
The errors which follow after that one I posted all seem to indicate that the LSM3 instance has been corrupted or not loaded correctly because the errors are things like "cannot invoke nil method Register", etc. on lines referencing LSM3.
I would think that if it is not a problem with AutoBar, I would still being seeing the bug while AutoBar is disabled...