I am almost back from holidays, so development will resume tomorrow sometime.
For the people wondering about what Ace does for a mod or AutoBar specifically:
1) Mod code is easily available and code changes can be and are submitted by other developers in the Ace comunity. Many of the people doing internationalization now use the SVN to submit their changes. I think SVN also helps them see what exactly changed & needs translation. AutoBar gained French and Spanish translation as result of becoming an Ace mod.
2) Sometimes when I log onto the Ace forums someone will bitch about some bug or pet peeve which I then fix right away. I can also get instant feedback this way as people tend to dl & test a new version right away.
3) Using the common PeriodicTable and other libraries lets those get upgraded independently of AutoBar, which is a good thing. If they also get used by other mods you use, then memory etc. is also saved which is even better.
4) The Ace community and the easily available code of all the ace mods gives me a pretty good idea of current "best practices".
Finally, don't confuse the pains of the 2.0 patch with the switch to Ace. The switch to Ace happenned quite a while ago. The switch to the 2.0 patch is not complete yet for AutoBar, and until then it remains a beta release with bugs & issues.
As mentioned below and elsewhere, the Ace label on a mod is no guarantee of quality. There are good, bad & ugly ace mods. The Ace conversion has made AutoBar a better mod though, and once the 2.0 patch changes are done it may actually feel that way when you use it ;-p
I'm getting a lot of ADDON_ACTION_BLOCKED errors like this when using Autobar :
Should be fixed now.
Quote from Maytrix »
Issues with Hunter, get the following errors when ever I log in my hunter....
[2006/12/29 07:54:13-1170-x2]: AutoBar-2.00.00.15 beta\Core.lua:798: attempt to index local 'button' (a nil value)
Do you still get this with 2.00.00.16?
Quote from Devla »
I haven't used AutoBar in a very long time, but I've added all the BC food and drinks to PeriodicTable-2.0
Nice. The latest zip should now include all these.
Quote from Amadeo »
Also, I noticed last night in PvP that each time I click a button on AutoBar (to use a Healthstone, in this case) my PC freezes up for a few seconds.
Since the latest revision (I think the one I am using is the revision just before your last post) I've been having a small graphic problem.
Since I used Bartender3 with the DreamLayout look I have always chose the Autobar to show the icons without the borders, I think the option is 'Plain Buttons'?
The problem is, unchecked; the buttons are normal - but checked it just well 'enlarges' the icons and doesn't remove the actual border. On the next reload, the 'enlarged' icons become smaller than the actual border itself so they are sitting in a sort of shell of a border.
I wish I could take a screenshot to show it, but I'm at work at the moment!
I'm getting a lot of ADDON_ACTION_BLOCKED errors like this when using Autobar :
Should be fixed now.
Still getting this kind of errors with the last revision :(
<event>ADDON_ACTION_BLOCKED:AddOn 'Ace2' tried to call the protected function 'AutoBarSSPopupHeaderFrame2:SetAttribute()'.
(tail call): ?:
!BugGrabber\BugGrabber.lua:480: in function <Interface\AddOns\!BugGrabber\BugGrabber.lua:452>
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateHeader.lua:483: in function <Interface\FrameXML\SecureStateHeader.lua:439>:
Interface\FrameXML\SecureStateHeader.lua:633: in function `SecureStateHeader_Refresh':
AutoBar-2.00.00.16 beta\Core.lua:1149: in function `ButtonsUpdate'
AutoBar-2.00.00.16 beta\Core.lua:1770: in function `LayoutUpdate'
AutoBar-2.00.00.16 beta\Core.lua:335: in function <Interface\AddOns\AutoBar\Core.lua:319>
<in C code>: ?
AceEvent-2.0-22135 (Ace2):319: in function `TriggerEvent'
AceEvent-2.0-22135 (Ace2):961: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:954>
Ok dumb question time...is it possible to add an integrated cooldown timer to autobar instead of having to run an independent one like OmniCC? Like I said I was just wondering so please don't set me ablaze with flames :P.
I definately noticed a difference when resizing the buttons, the lag there seems to be gone - which is great! I do still notice some freeze-lag when clicking the buttons quickly (stunlock, etc), though it's a bit better than it was. I hope there is still room for optimization!
Quote from: Maytrix on Yesterday at 11:59:03 am
Nope still getting the following error when loading my hunter
[2007/01/03 07:47:07-1247-x3]: AutoBar-2.00.00.16 beta\Core.lua:805: attempt to index local 'button' (a nil value)
That is very strange. I do not see how button can be nil when the code that passes it in already referenced a non-nill value of button. I added some debugging code though so if it happens again please post the stuff printed to chat just b4 the crash.
Also are all hunters crashing when using AutoBar or just a few people? (I have no hunter so no way to test & a level 1 hunter doesn't crash.)
On my hunter I do notice lag...more so than anyother class..
<event>ADDON_ACTION_BLOCKED:
AddOn 'Ace2' tried to call the protected function 'AutoBarSSPopupHeaderFrame2:SetAttribute()'
AceEvent-2.0-22135 (Ace2):319: in function `TriggerEvent'
Mmm, I thought I removed the call backs when going into combat. Are you using the embedded libraries or standalone?
Either way I added more checks for combat lockdown so this should not happen anymore.
Quote from ~*Katsume*~ »
Ok dumb question time...is it possible to add an integrated cooldown timer to autobar...?
It is possible. However rather than give the user a different custom implementation for each different mod I am hoping something universal like OmniCC can be used instead.
Quote from Maytrix »
Nope still getting the following error when loading my hunter
[2007/01/03 07:47:07-1247-x3]: AutoBar-2.00.00.16 beta\Core.lua:805: attempt to index local 'button' (a nil value)
That is very strange. I do not see how button can be nil when the code that passes it in already referenced a non-nill value of button. I added some debugging code though so if it happens again please post the stuff printed to chat just b4 the crash.
Also are all hunters crashing when using AutoBar or just a few people? (I have no hunter so no way to test & a level 1 hunter doesn't crash.)
Quote from Amadeo »
I do still notice some freeze-lag when clicking the buttons quickly (stunlock, etc), though it's a bit better than it was. I hope there is still room for optimization!
Weird, during combat lockdown there is not much of anything happening. I will try to see if I can reproduce this.
Quote from lapalapa »
getting error about profile at start
dont tell me i have to nuke my saved variables, please. spent hours tweaking all the stuff =(
Back in the old AutoBar days setting up custom buttons and removing others etc etc (basically customizing the bar) was very easy. Right now I just get lost in the myriad options and very very very unclear options. What's with the full page of empty buttons that I can click but can't actually change? It tells me I have to edit them somewhere else. I can't actually remove anything like before.
Basically put in my experience the whole setup of what to show and what not to show (and especially adding custom items) used to be nice and easy and now is totally F'ed up. Fix pls. :)
Back in the old AutoBar days setting up custom buttons and removing others etc etc (basically customizing the bar) was very easy. Right now I just get lost in the myriad options and very very very unclear options. What's with the full page of empty buttons that I can click but can't actually change? It tells me I have to edit them somewhere else. I can't actually remove anything like before.
Basically put in my experience the whole setup of what to show and what not to show (and especially adding custom items) used to be nice and easy and now is totally F'ed up. Fix pls. :)
Yeah I am not completely happy with that part. I have been thinking of adding an edit button that would take you to the relevant layer's edit of the slot / or just plain bringing up the relevant edit directly. I will also change the header to direct people to the slots tab instead of just saying not editable.
Btw, the slots tab is where you do the dragging & editing you are looking for.
Also, when editing the slot you can drag & drop to rearrange the order of items. That is another editing feature that is not clear just by looking at the categories. Perhaps I should add some text saying you can drag & drop but that seems so lame. Perhaps a help button would be better.
To make it simple I'd prefer having just one layer (character specific) and defaults for the most important items (Food, Water, Bandages, Health/Mana Potions).
I am fine with using my Heartstone out of the bag, have key bindings for my mount and just don't want to have a 20 buttons AutoBar... It was easy to setup in the old version.
To make it simple I'd prefer having just one layer (character specific) and defaults for the most important items (Food, Water, Bandages, Health/Mana Potions).
I am fine with using my Heartstone out of the bag, have key bindings for my mount and just don't want to have a 20 buttons AutoBar... It was easy to setup in the old version.
That is all in there already. Just go to the Profile tab and click on the "Single (Classic) Setup" button. Or click its reset button to do the setup as well as the relevant defaults. Then just empty out the slots you do not want.
It should be pain free to play with all the options as you can always click the revert button to get back to the old state.
I added a "Classic (Easy) AutoBar" section to the wiki to help people wade through the options.
For the people wondering about what Ace does for a mod or AutoBar specifically:
1) Mod code is easily available and code changes can be and are submitted by other developers in the Ace comunity. Many of the people doing internationalization now use the SVN to submit their changes. I think SVN also helps them see what exactly changed & needs translation. AutoBar gained French and Spanish translation as result of becoming an Ace mod.
2) Sometimes when I log onto the Ace forums someone will bitch about some bug or pet peeve which I then fix right away. I can also get instant feedback this way as people tend to dl & test a new version right away.
3) Using the common PeriodicTable and other libraries lets those get upgraded independently of AutoBar, which is a good thing. If they also get used by other mods you use, then memory etc. is also saved which is even better.
4) The Ace community and the easily available code of all the ace mods gives me a pretty good idea of current "best practices".
Finally, don't confuse the pains of the 2.0 patch with the switch to Ace. The switch to Ace happenned quite a while ago. The switch to the 2.0 patch is not complete yet for AutoBar, and until then it remains a beta release with bugs & issues.
As mentioned below and elsewhere, the Ace label on a mod is no guarantee of quality. There are good, bad & ugly ace mods. The Ace conversion has made AutoBar a better mod though, and once the 2.0 patch changes are done it may actually feel that way when you use it ;-p
Should be fixed now.
Do you still get this with 2.00.00.16?
Nice. The latest zip should now include all these.
Most of the lag should be gone with 2.00.00.16
Since the latest revision (I think the one I am using is the revision just before your last post) I've been having a small graphic problem.
Since I used Bartender3 with the DreamLayout look I have always chose the Autobar to show the icons without the borders, I think the option is 'Plain Buttons'?
The problem is, unchecked; the buttons are normal - but checked it just well 'enlarges' the icons and doesn't remove the actual border. On the next reload, the 'enlarged' icons become smaller than the actual border itself so they are sitting in a sort of shell of a border.
I wish I could take a screenshot to show it, but I'm at work at the moment!
Cheers
Edit: Ignore this, I need to learn2read :(
Still getting this kind of errors with the last revision :(
[2007/01/03 07:47:07-1247-x3]: AutoBar-2.00.00.16 beta\Core.lua:805: attempt to index local 'button' (a nil value)
---
I definately noticed a difference when resizing the buttons, the lag there seems to be gone - which is great! I do still notice some freeze-lag when clicking the buttons quickly (stunlock, etc), though it's a bit better than it was. I hope there is still room for optimization!
getting error about profile at start
dont tell me i have to nuke my saved variables, please. spent hours tweaking all the stuff =(
')' expected near 'Mana'
Nope still getting the following error when loading my hunter
[2007/01/03 07:47:07-1247-x3]: AutoBar-2.00.00.16 beta\Core.lua:805: attempt to index local 'button' (a nil value)
That is very strange. I do not see how button can be nil when the code that passes it in already referenced a non-nill value of button. I added some debugging code though so if it happens again please post the stuff printed to chat just b4 the crash.
Also are all hunters crashing when using AutoBar or just a few people? (I have no hunter so no way to test & a level 1 hunter doesn't crash.)
On my hunter I do notice lag...more so than anyother class..
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBut that may have changed in 2.0, but I doubt it.
Mmm, I thought I removed the call backs when going into combat. Are you using the embedded libraries or standalone?
Either way I added more checks for combat lockdown so this should not happen anymore.
It is possible. However rather than give the user a different custom implementation for each different mod I am hoping something universal like OmniCC can be used instead.
That is very strange. I do not see how button can be nil when the code that passes it in already referenced a non-nill value of button. I added some debugging code though so if it happens again please post the stuff printed to chat just b4 the crash.
Also are all hunters crashing when using AutoBar or just a few people? (I have no hunter so no way to test & a level 1 hunter doesn't crash.)
Weird, during combat lockdown there is not much of anything happening. I will try to see if I can reproduce this.
Fixed
Back in the old AutoBar days setting up custom buttons and removing others etc etc (basically customizing the bar) was very easy. Right now I just get lost in the myriad options and very very very unclear options. What's with the full page of empty buttons that I can click but can't actually change? It tells me I have to edit them somewhere else. I can't actually remove anything like before.
Basically put in my experience the whole setup of what to show and what not to show (and especially adding custom items) used to be nice and easy and now is totally F'ed up. Fix pls. :)
Yeah I am not completely happy with that part. I have been thinking of adding an edit button that would take you to the relevant layer's edit of the slot / or just plain bringing up the relevant edit directly. I will also change the header to direct people to the slots tab instead of just saying not editable.
Btw, the slots tab is where you do the dragging & editing you are looking for.
Also, when editing the slot you can drag & drop to rearrange the order of items. That is another editing feature that is not clear just by looking at the categories. Perhaps I should add some text saying you can drag & drop but that seems so lame. Perhaps a help button would be better.
I am fine with using my Heartstone out of the bag, have key bindings for my mount and just don't want to have a 20 buttons AutoBar... It was easy to setup in the old version.
That is all in there already. Just go to the Profile tab and click on the "Single (Classic) Setup" button. Or click its reset button to do the setup as well as the relevant defaults. Then just empty out the slots you do not want.
It should be pain free to play with all the options as you can always click the revert button to get back to the old state.
I added a "Classic (Easy) AutoBar" section to the wiki to help people wade through the options.
http://tuller.wowinterface.com
and before you say "it's not Ace"... it doesn't have to be. tuller writes good code, do not write it off because it's not on WAU.