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 can confirm that "right click targets pet" does not work even after reloads. I do think this is a big improvement, especially tying the hot keys to named slots rather than numbered (was really hard to figure out). I also saw the memory usage skyrocket but reloading the UI seems to fix that so it is probably tied to the changes not being implemented until a reload (and thus just stored/queued).
There have been some graphical errors when changing to less columns and 2 rows. I will post a picture as an edit in a few minutes. In the mean time, here is an error that occurred:
[2007/10/11 12:16:13-78-x4]: AutoBar-2.02.03.02 beta.38120\AutoBarClassBar.lua:478: attempt to perform arithmetic on local 'signX' (a nil value)
EDIT: Here is the picture I said I would add. My mouse (which you can't see in the picture) is floating over the the "4" on the left side of autobar itself. Basically there is nothing there, but it is showing up as a Flask.
-- 2.02.03.3 beta
-- Right Click on the moveable (green) bar now works & brings up the bar's options.
-- Added a "Move the Bars" option on the fuBar & miniMap dropdown options.
-- Style settings working, including cyCircled
-- Padding still needs reload
Quote from Ryvral »
Ok I just installed the alpha.. When I logged in the MOVE button was missing ... Any help would be freaking awesome as it is stuck in the middle of my screen
Please take some time to read the instructions in the first post on this thread. The old move button has been replaced with a Bartender3 style moving scheme.
In addition there is now a "Move the Bars" option on the fuBar & miniMap menus.
Quote from godzmack »
Any chance of getting the old "change the spacing between items" in the options? :>
The padding should now work, although it needs reload due to another bug.
...I instituted the configuration management discipline in our department and have done so at several companies...
Really, the issue here is that WoWAce needs a release mechanism. A lot of effort has gone into making it easy for people to use WAU to get the latest alpha beta gamma or whatnot release daily or even more frequently.
In reality very few people need a constant feed of fresh SVN builds. The vast majority of people need to repeatedly get a mod around the time a big patch ships & then do nothing till the next patch. If they are energetic, they update to the latest release on say curse or WoWUI or in the case of AutoBar http://code.google.com/p/autobar/
So if you want this issue fixed, its not about making Authors go use another SVN then post releases on this SVN. It is about making the wowace community institute a release mechanism that is separate from the dev SVN. There are threads about that all over, just use the search function at the top of this page. This thread is for AutoBar discussion though so I don't really want to repeat the other threads here once again. The bottom line is this is a dev SVN. If you insist on turning it into something like WoWUI that is mostly for stable releases then someone will have to create a wowwowace site where we can once more have a dev environment. But that is silly since we already have one right here. So go forth & start a thread somewhere about getting an official release mechanism for stuff in the SVN.
Meanwhile as an author I have gone to the trouble of setting up a google code site for official releases. There is a wiki on this site that points to it. The first post of this thread points to it. If you go there you can download the old official release from the home page. You will see absolutely no mention of an alpha, unless you go to downloads & download one.
You will however see mention of coming here for frequent "nightly" style builds.
Upon startup, after deleting WTF files in saved variables.
I immediately used the config to adjust the autobar to my preferred 4x4 configuration. I use cycircled so i understand this is not truly working but the look at the moment seems to be ok right now. After making the 4x4 arrangement all the numbers for remaining items within the buttons stay in their horizontal position, so I have 16 buttons but the original row is still a horizontal row of 16 buttons that are not their with their qty still there. I hope that makes sense, after a /rl no problems then.
I have a stack of buff food that when I hover over the bottom food the two other options appear as as see through boxes over the other two original categories present. However when I hover over the pop-up buttons I then see the tooltip for the other buff foods i have in the category.
I really like where this is headed, but it looks like you have a lot of code to add and refine, and us QA personnel have a lot of testing to help you get through it.
Looking forward to helping anyway I can.
Got this error after making the above adjustments.
[2007/10/11 17:33:03-1519-x1]: <event>ADDON_ACTION_BLOCKED:AddOn 'Ace2' tried to call the protected function 'ReloadUI()'.
<in C code>: in function `ReloadUI'
nQuestLog-1.0\core.lua:425: in function <Interface\AddOns\nQuestLog\core.lua:421>
<in C code>: in function `pcall'
AceAddon-2.0-46764 (Ace2):24: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:23>
AceAddon-2.0-46764 (Ace2):999: in function `ManualEnable'
AceAddon-2.0-46764 (Ace2):927: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:920>
<in C code>: ?
AceEvent-2.0-49307 (Ace2):266: in function `TriggerEvent'
AceEvent-2.0-49307 (Ace2):962: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:955>
IU saw you made an update to the code during my initial test, so I will join in on your fun.
Ok, just updated my mods via WAU (WoW Ace Updater) and I got this new version of Autobar. Now, I'm with that I'm kind of torn on if I like it or not.
I've been using autoBar since pretty near it's creation date. It's been a godsend. I want to give out many props for al lyour work as I've never posted before. Great work.
Now, this new version, I can see it's heading in a great direction. I love what yo uare doing with it. The problem I have with it is this. It's not quite stable yet. That in turn affects me in raids and what not. (yes, I'm kind of dependent on autobar. LoL
Some of the issues I've noticed thus far are, sometimes it doesnt' update items on the list properly. For example. I used my last healing potion, the button disappeared as it should, the mana potion scooted over to where the heal potion was (everything else scooted over as well). Problem is, when I went to use my mana potion, it was still trying to use the heal potion. The place where my mana potion was is now where my water was, but like the new placement of the mana potion, it was still reading what used to be there. (the mana potion)
I hope i explained that correctly... LoL, because reading over it, I almost confuse myself. Another issue I've noticed is the docking. It won't dock to my Bartender bars like it used to. I've also noticed that the padding option has an issue. it's set to 1, but all the buttons aren't really side by side. I went and changed the padding to -20, yet the spacing between the buttons hadn't changed at all.
Once again, I love the direction you are taking this, but, the whole reason I am posting this, is I wanted to know if you could post the last update of your previous version somewhere. I've always used WAU for updating, so have no real zip/rar of the old version. I run two machines so I will continue to fiddle and test the new version, but when it comes to raiding, i'd love to be able to use the old version on my other machine. Any chance of this?
If you don't like the new version and want to go back to the old one, then download this http://files.wowace.com/AutoBar/AutoBar-r51227.7.zip, delete your current ..\Interface\AddOns\AutoBar folder, extract the zip into your AddOns folder, and you're good to go. If you use WAU, don't forget to right click AutoBar/AutoBarConfig in the addons list and set them to be ignored (otherwise you'll just overwrite it the next time you update via WAU)...
Screw all these spoiled kiddies complaining about stable releases when they have no idea what they are doing or talking about, learn to read befor talking crap to a mod dev that has gven their free time to keeping one hell of a mod available for FREE for YOU to USE for Free.
If you have an issue with this mod then go back and get the STABLE release.
You have no right to flame a dev when you are downloading from a DEV SVN.
Getting tired of the constant disrespect I keep seeing time and time again focused at a dev who is making THEIR mod the way THEY want it and sharing it with their community.
If you dont like what they have done to their mod then delete it or learn to code and make changes in the code to allow it to work the way you like, I do this often, if I dont like something I change it and then send my SUGGESTIONS to the author.
Until then learn some respect and learn to thank these guys for all their hard work and time they give to us for FREE.
I for one thank them all for their hard work and ask they overlook these asshats who show no respect. Let them complain they can use something else if they dont like it.
...For example. I used my last healing potion, the button disappeared as it should, the mana potion scooted over to where the heal potion was (everything else scooted over as well). Problem is, when I went to use my mana potion, it was still trying to use the heal potion.
Yes there is an issue with updating the buttons right now. I will fix it for the next patch. This will also fix the horrible memory leak esp while changing settings.
If you have useful feedback, post it. If you update all your addons every day and you don't like the current version, roll back, stop updating obsessively, and keep your opinions about the current state of the addon to yourself.
Left it running on my bank alt unintentionally, so decided to post a list of stuff I noticed with quick testing.
- dragging sliders in the config gui doesn't work for some reason - you have to click all over the slider to set it where you want (or type in the box)
- alpha setting doesn't work
- show count text doesn't work
- show empty buttons has no noticeable effect
- bars->basic->enabled does not work
- fadeout does not work
- setting the rows to 1 and columns to less than 14 or so results in a 2-row display despite the 1 row setting
- button width/height have no effect
- "dock to" does not work
- "dock to" does not include pet or stance bars
- count text seems misaligned after having played with scaling and padding settings