Please label your issue as being a bug or missing item or feature request by clicking in the "Labels" fields!
Beta
The beta is now live on the SVN. Yes, you will need to make some changes:
Notes:
You need ButtonFacade to skin AutoBar
You need the latest cyCirled if you use it to skin other mods
You double click on the AutoBar fuBar icon or minimap icon or type "/atb" to bring up the config
If you report errors with this make sure you also post the version as displayed in the config window title.
How do I wrangle my bars?
You can hide a new bar by shift clicking on the AutoBar button on the minimap or FuBar. This makes it green & draggable. Click on it to cycle it between red and green. Drag it around to move it where you want it. Red BArs are hidden, this is different from disabling them. If you shift click on the AutoBar button again then all the red bars disapear and any "green" bars remain. If you use Bartender3 you should be familiar with this process.
How do I herd my buttons?
You can move buttons by control clicking on the AutoBar button on the minimap or FuBar. This shows all buttons on the bar and you can drag & drop them to rearrange them. The Bars will have a purple background and active Buttons will be bordered in green, disabled in red, and inactive in blue.
The Invisible Man Release
See first post for details.
Quote from OrionShock »
so... your google svn is empty.. so is this going to be by zip file alpha/beta testing only ?
No, real soon now the alpha will be usable enough to move into beta & thus onto wowace SVN. Meanwhile I use Perforce on my local machine so I do not miss out on revision control.
might i suggest for the sake of sanity, that you up the Major version.. ie AutoBar2 if your going to be making life changing changes to this new version :D
I think that is a good idea. There are *a lot* of changes between this and the previous version.
There are a lot of changes. I am hoping setup & use is easier than before. The layered prefs was just impossible to explain or get a good ui for. Clicking enable / disable on a list of buttons seems easier to me. I will be looking at Rock or whatever other new config tools emerge as an update over waterfall which is a bit dated in comparison or at least not seeing active development.
Don't really want to call it AutoBar2, it will remain AutoBar. The actual mod's functionality is not changing, just getting better with a different config. The version scheme is basically blizzards with an extra field tagged on. I like it because it gives you an idea of what version of WoW it is tracking.
I think the point is that there have been a few major version releases of other addons recently where the upgrade process was not invisible. In fact, in some cases it was downright backwards incompatible leading to some very irate users who lost their painstakingly configured settings.
If you are going to keep it AutoBar, please make sure that the user's config is properly converted or at least preserved so that they can switch back.
2nd bar question, this may be a path you don't care to go down, but
is it possible to rename and edit a couple of files to make it have
a new name/saved variables,new directory.. basically make a new clone
add thereby having 2 bars till you get that feature in the main add..
1) Best- list of files to rename and edits to make..
2) next- yes it is doable and would work but you are on your own.
3) last- because of some programing api issues etc..., this would not work...
Of course I would assume anyone doing this would be on their own and you
would not support it.
My apologies if this is not the appropriate place to bring this up but didn't
seem to go in bug report section. Just installed yesterday and is a great
add!
I think the point is that there have been a few major version releases of other addons recently where the upgrade process was not invisible. In fact, in some cases it was downright backwards incompatible leading to some very irate users who lost their painstakingly configured settings.
If you are going to keep it AutoBar, please make sure that the user's config is properly converted or at least preserved so that they can switch back.
It should be 100% revertable since the new prefs are using the ace db stuff & the old ones were completely separate. I am also still loading AutoBar_Config which held the old settings so if you go back to the old mod it would be as if nothing happened.
The keybinds are now to a specific button not a particular button that happen to be in a specific spot. So you would need to bind the new keys. The old 1-24 keys are still there so you would not lose the old settings unless u rebind them. Thats the only change that can not be reverted that I can think of.
... basically make a new clone
add thereby having 2 bars till you get that feature in the main add...
This is not necessary as the new bar is feature complete compared to the old one. All the features listed as still needing to be done are not in the old bar to begin with.
This is not necessary as the new bar is feature complete compared to the old one. All the features listed as still needing to be done are not in the old bar to begin with.
I thought a second/splittable bar was still on the wish list.
Not sure what you mean by old bar.. I just started using it
yesterday and only have one bar which I assume is the new bar?
[2007/10/08 11:32:06-1267-x406]: AutoBar-2.02.02.14 alpha.38120\Core.lua:667: attempt to index field 'ssButtons' (a nil value)
bugsack is bursting with this. noticed it happen on a reset and whenever i hover over a button. the popups are not showing icons and my custom buttons are not showing, only the 'stock' buttons work.
[2007/10/08 11:32:06-1267-x406]: AutoBar-2.02.02.14 alpha.38120\Core.lua:667: attempt to index field 'ssButtons' (a nil value)
bugsack is bursting with this. noticed it happen on a reset and whenever i hover over a button. the popups are not showing icons and my custom buttons are not showing, only the 'stock' buttons work.
Yeah ironically buggrabber craps out if there are more than 20 errors per second & then doesnt log any at all so I missed this. Im hacking in some macro buttons & once that is stable I will post an update.
I thought a second/splittable bar was still on the wish list.
Not sure what you mean by old bar.. I just started using it
yesterday and only have one bar which I assume is the new bar?
I am working on a Druid bar right now that will have a bunch of druid form macros. This will test out the multiple bar thing. I still have to add support for actuall ycreating new bars & assigning buttons to them other than via the default prefs.
Yeah ironically buggrabber craps out if there are more than 20 errors per second & then doesnt log any at all so I missed this. Im hacking in some macro buttons & once that is stable I will post an update.
http://code.google.com/p/autobar/downloads/list
-- 2.02.02.15 alpha
-- Some bug fixes. Popups should be working now along with arrange on use of them including spells.
-- Some under the cover work on macro buttons.
-- Multiple bars working. Only Druids will see an extra bar for now.
Quote from jerry247 »
nice, excited about macros
Yeah me too. The ones I am working on should make it so I have working cat, travel, & bear macros regardless of raid arena or farming spec.
Once I get the issues resolved with those I will make macro categories as well so 1 button can have a variety of class specific macros. Its more involved than I thought, probably need some kind of variable substitution scheme as well.
I also need to add support for the built in sets of macros for character (18) & general (18) as well.
Oh yes, and if there are no major bugs or issues im going beta tomorrow so think of this as a beta candidate.
Do we still need the AutoBar_Config addon or is it all encompassed in Autobar by itself now?
Nope, you can drop that if u switch to the alpha. It may come back if I find a good way to isolate the gui stuff but its pretty lightweight now since waterfall & later rock are doing all the work.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Official STABLE releases & docs for the current version: http://code.google.com/p/autobar/
How to Use AutoBar http://code.google.com/p/autobar/wiki/Usage.
Debugging: Don't be noob, please follow http://www.wowace.com/wiki/Debugging b4 you post.
Report Missing Items
Report bugs, Make feature or documentation Requests
Please label your issue as being a bug or missing item or feature request by clicking in the "Labels" fields!
Beta
The beta is now live on the SVN. Yes, you will need to make some changes:
Notes:
- You need ButtonFacade to skin AutoBar
- You need the latest cyCirled if you use it to skin other mods
- You double click on the AutoBar fuBar icon or minimap icon or type "/atb" to bring up the config
- If you report errors with this make sure you also post the version as displayed in the config window title.
How do I wrangle my bars?You can hide a new bar by shift clicking on the AutoBar button on the minimap or FuBar. This makes it green & draggable. Click on it to cycle it between red and green. Drag it around to move it where you want it. Red BArs are hidden, this is different from disabling them. If you shift click on the AutoBar button again then all the red bars disapear and any "green" bars remain. If you use Bartender3 you should be familiar with this process.
How do I herd my buttons?
You can move buttons by control clicking on the AutoBar button on the minimap or FuBar. This shows all buttons on the bar and you can drag & drop them to rearrange them. The Bars will have a purple background and active Buttons will be bordered in green, disabled in red, and inactive in blue.
See Docs for the beta http://code.google.com/p/autobar for full details.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSee first post for details.
No, real soon now the alpha will be usable enough to move into beta & thus onto wowace SVN. Meanwhile I use Perforce on my local machine so I do not miss out on revision control.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere are a lot of changes. I am hoping setup & use is easier than before. The layered prefs was just impossible to explain or get a good ui for. Clicking enable / disable on a list of buttons seems easier to me. I will be looking at Rock or whatever other new config tools emerge as an update over waterfall which is a bit dated in comparison or at least not seeing active development.
Don't really want to call it AutoBar2, it will remain AutoBar. The actual mod's functionality is not changing, just getting better with a different config. The version scheme is basically blizzards with an extra field tagged on. I like it because it gives you an idea of what version of WoW it is tracking.
If you are going to keep it AutoBar, please make sure that the user's config is properly converted or at least preserved so that they can switch back.
is it possible to rename and edit a couple of files to make it have
a new name/saved variables,new directory.. basically make a new clone
add thereby having 2 bars till you get that feature in the main add..
1) Best- list of files to rename and edits to make..
2) next- yes it is doable and would work but you are on your own.
3) last- because of some programing api issues etc..., this would not work...
Of course I would assume anyone doing this would be on their own and you
would not support it.
My apologies if this is not the appropriate place to bring this up but didn't
seem to go in bug report section. Just installed yesterday and is a great
add!
It should be 100% revertable since the new prefs are using the ace db stuff & the old ones were completely separate. I am also still loading AutoBar_Config which held the old settings so if you go back to the old mod it would be as if nothing happened.
The keybinds are now to a specific button not a particular button that happen to be in a specific spot. So you would need to bind the new keys. The old 1-24 keys are still there so you would not lose the old settings unless u rebind them. Thats the only change that can not be reverted that I can think of.
This is not necessary as the new bar is feature complete compared to the old one. All the features listed as still needing to be done are not in the old bar to begin with.
I thought a second/splittable bar was still on the wish list.
Not sure what you mean by old bar.. I just started using it
yesterday and only have one bar which I assume is the new bar?
bugsack is bursting with this. noticed it happen on a reset and whenever i hover over a button. the popups are not showing icons and my custom buttons are not showing, only the 'stock' buttons work.
Yeah ironically buggrabber craps out if there are more than 20 errors per second & then doesnt log any at all so I missed this. Im hacking in some macro buttons & once that is stable I will post an update.
I am working on a Druid bar right now that will have a bunch of druid form macros. This will test out the multiple bar thing. I still have to add support for actuall ycreating new bars & assigning buttons to them other than via the default prefs.
nice, excited about macros
Getting rid of bugs & old AutoBar ghosts.
See first post for more details
http://code.google.com/p/autobar/downloads/list
-- 2.02.02.15 alpha
-- Some bug fixes. Popups should be working now along with arrange on use of them including spells.
-- Some under the cover work on macro buttons.
-- Multiple bars working. Only Druids will see an extra bar for now.
Yeah me too. The ones I am working on should make it so I have working cat, travel, & bear macros regardless of raid arena or farming spec.
Once I get the issues resolved with those I will make macro categories as well so 1 button can have a variety of class specific macros. Its more involved than I thought, probably need some kind of variable substitution scheme as well.
I also need to add support for the built in sets of macros for character (18) & general (18) as well.
Oh yes, and if there are no major bugs or issues im going beta tomorrow so think of this as a beta candidate.
Nope, you can drop that if u switch to the alpha. It may come back if I find a good way to isolate the gui stuff but its pretty lightweight now since waterfall & later rock are doing all the work.