One question and one bug found in SVN rev 51654 (2.02.03.01 beta).
Question: am I being dense, or is there no way to bind a key to the "water" button? I've looked through bindings.xml, and it just seems to be missing, though there are bindings for Food, etc. Is there some way to create a new dynamic key binding for categories? If so I can see why this would be neat for people creating completely new categories, but isn't water something that should be in the base distro? Personally the only bound keys I used on the old AutoBar were bandage, food, and water - everything else I clicked on as needed.
Bug: this is minor. If you shift-click the AutoBar icon to make the bars go green, then while they are green disable one (in my case the druid bar, which I hadn't really wrapped my head around until I saw it's outline), then shift-click the icon again, the druid bar remains on screen in green while the other active bar becomes locked again. I'm sure it's just how the bars are being iterated over in the shift-click handler; perhaps ignoring the "enabled" state of the bar during that handler would be a good idea - even though what I did to cause it to happen can easily be attributed to "stupid user syndrome". If you follow through with other bars for other classes, it might become more prevalent.
Thanks for all the work. Came as a bit of a surprise, but everything seems to be working for me save the water key binding right now.
Seems to be working pretty well for me... Only issue I'm having (and I haven't ready all the recent posts to see if it's been mentioned) is that I need to reload my UI to get pretty much any change to take effect.
[2007/10/11 16:57:32-291-x1]: AutoBar-2.02.03.02 beta.38120\AutoBarOptions.lua:1053: invalid option in `format'
AceAddon-2.0-46764 (Ace2):483: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:460>
<in C code>: ?
AceEvent-2.0-49307 (Ace2):303: in function `TriggerEvent'
AceEvent-2.0-49307 (Ace2):962: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:955>
Trying to open config window via shortcut:
[2007/10/11 16:59:37-291-x1]: Waterfall-1.0-51659 (Waterfall-1.0):505: attempt to index field '?' (a nil value)
AutoBar-2.02.03.02 beta.38120\Core.lua:131: in function `ConfigToggle'
<string>:"AUTOBAR_CONFIG":1: in function <[string "AUTOBAR_CONFIG"]:1>
and double clicking Autobar icon:
[2007/10/11 17:00:35-291-x1]: Waterfall-1.0-51659 (Waterfall-1.0):445: You cannot open a waterfall without registering it first
Waterfall-1.0-51659 (Waterfall-1.0):445: in function `Open'
AutoBar-2.02.03.02 beta.38120\AutoBarFuBar.lua:67: in function `OnDoubleClick'
FuBarPlugin-2.0-48629:952: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:950>
The defaults buttons seem to work properly,
but cant access any config window.
Can unlock the bars, and move them.
But cant unlock the buttons (no error, just it appears i cant move them)
This new version will be awesome when it will work, thank you for your work :)
But i please have a request:
I'm really ok to help you with debugging and development, but i need autobar for raiding and playing Wow.
Could you please rename to autobar2, or at least renaming the "old one" so that we (i) can all the 2 installed and load working version when raiding?
- Padding is stuck. There are always stuck with gapping spots between buttons.
- On scaling buttons stick outside the green moving area when u turn it on..
- Changing width/height
- Seems u need to reload to fix config issues regarding to resize and moving bar.. or u get numbers all over the screen.
I do concur with requests for it to be AutoBar2. I've used your addon since the beginning and I would have upgraded to AB2 in a whim on my non-raiding computer.. :)
This is not correct. If you read the instructions they say to click the AutoBar icon. Clicking fubar just gives u fubar options.
I didn't get an Autobar icon. There is a FuBar menu item in FuBar, nothing on the minimap, and no way to show an icon in the configuration screen. The old drag handle is not there at the corner of the bar. There is always the possibility that it is hidden behind another minimap icon.
Shift-clicking on the FuBar menu item icon does nothing that I can see. No red/green glow.
I have loved Autobar in the past, back when Saien introduced the package along with Totembar. It is an essential part of my UI, and will likely replace Cryolysis and a couple of other add-ons once it is finished.
In the meantime, I don't have a way to move the Autobar bar, and cannot use any style other than dreamy because the scaling shifts the click regions.
That's a bit dramatic. Once again, WAU spoils the children.
Er, dramatic for effect. You don't remember when the Cosmos updater would run and effectively delete every non-Cosmos add-on in your Addons folder.
Well, JWowAceUpdater now runs and overwrites every working Ace add-on with a not-guaranteed-to-work Ace add-on.
I instituted the configuration management discipline in our department and have done so at several companies. One of the first rules I teach my programmers: don't check beta code into the trunk. The Ace developers have not yet learned this little lesson, and will be poorer for not having figured it out on their own. Similarly, The three different developers for WowAceUpdater, MacAceUpdater and JWowAceUpdater have no understanding of trunk and branch updates as they indiscriminately propagate bad code into the wilderness, and blame the end-user for failing to read the fine print. This is developer arrogance at its finest.
I will say no more, as I sense an ivy covered tower here, and wouldn't want to let some light in.
Toad, you are a class act. dunno how you guys put up with all the intolerance and self-entitlement BS from so many of the users. its a game...go get some sun, people.
all of the problems i've had with the new version have been mentioned already, excepting for the "right click targets pet" function (actually not positive i did a reload after changing that option tho). i was able to get it functioning at a more-than-acceptable level with only a few minutes of fiddling and /reload-ing.
looking forward to all the new functionality and new configuration getting ironed out and am more than happy to put up with a few warts in the meantime.