This may be working now, but I wont have a mage till tbc, and I have no warlock at all to test on. Right click on the category should do the cast.
Also did right click to do travel forms for Shammies & Druids, & summoned mounts for warlocks & palies.
Tried this on my mage. Summoning food and water works great. But mana stones haven't been implemented yet. (drank a few potions by accident, :( )
One thing with the food/water though. Right now, no autobar button appears when there is no food/water in my inventory. So I can't right click to summon more. Is there any way a darkened icon can appear for mages so when they log in they can immediately summon more water/food?
Great work, though, thanks for implementing this feature!
I've yet to test on my warlock's healthstones. Will report back when I do.
Tried this on my mage. Summoning food and water works great. But mana stones haven't been implemented yet. (drank a few potions by accident, :( )
One thing with the food/water though. Right now, no autobar button appears when there is no food/water in my inventory. So I can't right click to summon more. Is there any way a darkened icon can appear for mages so when they log in they can immediately summon more water/food?
Ok I changed it to scan for the highest castable item, so manastones may work now. You may want to add the stone category to an empty slot to test. If the stones are unique then they will not work as I have it currently. Dang not having a mage to test with.
I am still thinking about how to best finish the implementation of this feature so for now it is only while the category shows. I will probably finally do named slots and have castable items attached to the slot itself, instead of to a category in it that may or may not be the top one.
Quote from Grita »
I'm getting some insane stuttering with Autobar enabled, but *only* with my hunter when she has her pet out. It makes playing my hunter w/pet very difficult so I've got Autobar turned off with her.
I think the issue is with the button update code being called excessively. I will throttle that down when I get back. Meanwhile I want to leave a stable version while I am gone, so sorry for the hassle.
Well I am off for the holidays, so have fun during this gift receiving season. I will be back just b4 the New Year.
i've removed all autobar.* from WTF folders and still have many errors:
1. buttons sizing working wrong. item icons like 2 times less than they should be (border around seems ok) and step between buttons made by icon size i think, so borders overlap (there was screenshot for this issue above in this thread). i need to set gapping 17 with button size 24 to get them not overlapping but item icons still very small.
2. Plain buttons isn't working
3. Looks like "Show Category Icons" works instead of "Show Empty Buttons" and "S E B" does nothing
Also have some question - is it possible to go to next item in category while in combat ?
1. buttons sizing working wrong. item icons like 2 times less than they should be (border around seems ok) and step between buttons made by icon size i think, so borders overlap (there was screenshot for this issue above in this thread). i need to set gapping 17 with button size 24 to get them not overlapping but item icons still very small.
2. Plain buttons isn't working
3. Looks like "Show Category Icons" works instead of "Show Empty Buttons" and "S E B" does nothing
1) I am unable to reproduce this. I have gapping 3 & the buttons behave correctly at all sizes with no overlap.
2) Correct. This is still a beta & I would say I am maybe 60% or 70% of the way through reimplementing everything.
3) Correct, "Show Empty Buttons" has not been reimplemented yet.
Idk about others, but I wanted the items to fade in and out depending if they're usable (i.e. mount fades out in combat, fades back to normal when OOC.)
The code was in there and there was a "TODO:" but it was always saying the item is usable
In "Autobar/Core.lua" there is a function called "function AutoBar_Button_UpdateUsable()"
I replaced the line:
local isUsable = true;
with:
local isUsable, notEnoughMana = IsUsableItem(itemId);
Tried this on my mage. Summoning food and water works great. But mana stones haven't been implemented yet. (drank a few potions by accident, :( )
One thing with the food/water though. Right now, no autobar button appears when there is no food/water in my inventory. So I can't right click to summon more. Is there any way a darkened icon can appear for mages so when they log in they can immediately summon more water/food?
Ok I changed it to scan for the highest castable item, so manastones may work now. You may want to add the stone category to an empty slot to test. If the stones are unique then they will not work as I have it currently. Dang not having a mage to test with.
I am still thinking about how to best finish the implementation of this feature so for now it is only while the category shows. I will probably finally do named slots and have castable items attached to the slot itself, instead of to a category in it that may or may not be the top one.
Quote from Grita »
I'm getting some insane stuttering with Autobar enabled, but *only* with my hunter when she has her pet out. It makes playing my hunter w/pet very difficult so I've got Autobar turned off with her.
I think the issue is with the button update code being called excessively. I will throttle that down when I get back. Meanwhile I want to leave a stable version while I am gone, so sorry for the hassle.
Well I am off for the holidays, so have fun during this gift receiving season. I will be back just b4 the New Year.
Thanks for adding this. Keep up the good work and have a great and safe holiday!
First off, thanks for making Autobar an Ace addon. It was good before, it's great now. However, I do note an issue upon initial load on where Autobar gets placed. With no docking enabled, and Autobar moved to the lower right-hand corner, whenever I log in, appx. half the bar gets pushed offscreen. If I load the config addon, the bar jumps to where I'd originally placed it. I'm presuming this means that one of the functions required for placement isn't saving correctly in Autobar's settings. As a workaround, I'd like to set up Autobar Config to always load, not just load-on-demand, but a permafix would be nice too. Thanks again.
First off, thanks for making Autobar an Ace addon. It was good before, it's great now. However, I do note an issue upon initial load on where Autobar gets placed. With no docking enabled, and Autobar moved to the lower right-hand corner, whenever I log in, appx. half the bar gets pushed offscreen. If I load the config addon, the bar jumps to where I'd originally placed it. I'm presuming this means that one of the functions required for placement isn't saving correctly in Autobar's settings. As a workaround, I'd like to set up Autobar Config to always load, not just load-on-demand, but a permafix would be nice too. Thanks again.
Two things.. first off, why do people keep saying that, now that an AddOn is using Ace Shared Libraries, it's magically better all of a sudden? I imagine it helps some with keeping Toadkiller sane from a coding point of view but my Ace-enabled AddOns do not glow or shine with an aura of Ace-power that sets it apart from the rest. They don't all use less memory than before. None of my Ace AddOns share a consistent configuration UI. And a great many, including this fine one, have bugs. All I can truly attribute to Ace is that it might make a programmer's life easier when creating WoW mods, adds at least one extra folder to the AddOn for the On Demand config file, and puts green text in the AddOn window so that I know it is made with Ace. Can you please tell me why you (and others I've seen) say that Ace automatically makes it great?
And secondly, if you open AutoBarConfig.toc and find the LoadOnDemand entry, I believe if you change the ## LoadOnDemand: 1 to ## LoadOnDemand: 0 or delete it altogether, that will make it load when all the other AddOns are loaded as well. I haven't tested it myself but my primitive understanding of LUA suggests this to be how it works.
Is it possible to use autobar items via macros/scripts? It would be a great way to make a "panic" button that would automatically use whatever healing item is ready: healthstone, healing pot, etc., or for a warrior add it to script that would trigger last stand, LGG, etc.
Two things.. first off, why do people keep saying that, now that an AddOn is using Ace Shared Libraries, it's magically better all of a sudden? I imagine it helps some with keeping Toadkiller sane from a coding point of view but my Ace-enabled AddOns do not glow or shine with an aura of Ace-power that sets it apart from the rest. They don't all use less memory than before. None of my Ace AddOns share a consistent configuration UI. And a great many, including this fine one, have bugs. All I can truly attribute to Ace is that it might make a programmer's life easier when creating WoW mods, adds at least one extra folder to the AddOn for the On Demand config file, and puts green text in the AddOn window so that I know it is made with Ace. Can you please tell me why you (and others I've seen) say that Ace automatically makes it great?
Two reasons above and beyond ones you already highlighted (easier for new programmers, and reduced memory usage):
The use (and reuse) of common libraries can make complex addons more easily understood, hacked and improved by other authors. Hackability is a good thing.
Autobar had been orphaned by its original author (Saien) when he left WoW. It remained somewhat functional for several months, but it was definitely showing its age. When Toadkiller took it over, he improved it substantially and restored luster to one of the best addons ever.
And secondly, if you open AutoBarConfig.toc and find the LoadOnDemand entry, I believe if you change the ## LoadOnDemand: 1 to ## LoadOnDemand: 0 or delete it altogether, that will make it load when all the other AddOns are loaded as well. I haven't tested it myself but my primitive understanding of LUA suggests this to be how it works.
My primitive understanding of LUA is clearly more primitive than yours, but that surely makes sense to me :) I'll give it a shot. Thanks.
I've noticed a lot of resource use when doing things with AutoBar. One of them is during resizing buttons. My PC will freeze up for a few seconds each time they resize. 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. Hopefully you can fix it!
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.
I narrowed this down more specifically. When I mouse over a button and click it, there is no lag. However, if I then click it a second time without first moving the cursor out of that button's mouse over, the UI lags up significantly. This is especially noticeable if you spam click a button (for example when it is about to come out of cooldown) and my perceived fps goes into low single digits.
I'm getting a lot of ADDON_ACTION_BLOCKED errors like this when using Autobar :
<event>ADDON_ACTION_BLOCKED:AddOn 'Ace2' tried to call the protected function 'AutoBarSAB24:Hide()'.
(tail call): ?:
!BugGrabber\BugGrabber.lua:481: in function <Interface\AddOns\!BugGrabber\BugGrabber.lua:450>
<in C code>: in function `Hide'
Interface\FrameXML\SecureStateHeader.lua:484: in function <Interface\FrameXML\SecureStateHeader.lua:439>:
Interface\FrameXML\SecureStateHeader.lua:633: in function `SecureStateHeader_Refresh':
AutoBar-2.00.00.15 beta\Core.lua:1140: in function `ButtonsUpdate'
AutoBar-2.00.00.15 beta\Core.lua:1761: in function `LayoutUpdate'
AutoBar-2.00.00.15 beta\Core.lua:328: in function <Interface\AddOns\AutoBar\Core.lua:312>
<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>
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Tried this on my mage. Summoning food and water works great. But mana stones haven't been implemented yet. (drank a few potions by accident, :( )
One thing with the food/water though. Right now, no autobar button appears when there is no food/water in my inventory. So I can't right click to summon more. Is there any way a darkened icon can appear for mages so when they log in they can immediately summon more water/food?
Great work, though, thanks for implementing this feature!
I've yet to test on my warlock's healthstones. Will report back when I do.
Ok I changed it to scan for the highest castable item, so manastones may work now. You may want to add the stone category to an empty slot to test. If the stones are unique then they will not work as I have it currently. Dang not having a mage to test with.
I am still thinking about how to best finish the implementation of this feature so for now it is only while the category shows. I will probably finally do named slots and have castable items attached to the slot itself, instead of to a category in it that may or may not be the top one.
I think the issue is with the button update code being called excessively. I will throttle that down when I get back. Meanwhile I want to leave a stable version while I am gone, so sorry for the hassle.
Well I am off for the holidays, so have fun during this gift receiving season. I will be back just b4 the New Year.
i've removed all autobar.* from WTF folders and still have many errors:
1. buttons sizing working wrong. item icons like 2 times less than they should be (border around seems ok) and step between buttons made by icon size i think, so borders overlap (there was screenshot for this issue above in this thread). i need to set gapping 17 with button size 24 to get them not overlapping but item icons still very small.
2. Plain buttons isn't working
3. Looks like "Show Category Icons" works instead of "Show Empty Buttons" and "S E B" does nothing
Also have some question - is it possible to go to next item in category while in combat ?
1) I am unable to reproduce this. I have gapping 3 & the buttons behave correctly at all sizes with no overlap.
2) Correct. This is still a beta & I would say I am maybe 60% or 70% of the way through reimplementing everything.
3) Correct, "Show Empty Buttons" has not been reimplemented yet.
Did you mean AutoBar 20915?
The code was in there and there was a "TODO:" but it was always saying the item is usable
In "Autobar/Core.lua" there is a function called "function AutoBar_Button_UpdateUsable()"
I replaced the line:
local isUsable = true;
with:
local isUsable, notEnoughMana = IsUsableItem(itemId);
Haven't gotten any errors and it works fine.
Thanks for adding this. Keep up the good work and have a great and safe holiday!
i put it into a slot from my bag
then i push the button nothing happens
what is my mistake ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTwo things.. first off, why do people keep saying that, now that an AddOn is using Ace Shared Libraries, it's magically better all of a sudden? I imagine it helps some with keeping Toadkiller sane from a coding point of view but my Ace-enabled AddOns do not glow or shine with an aura of Ace-power that sets it apart from the rest. They don't all use less memory than before. None of my Ace AddOns share a consistent configuration UI. And a great many, including this fine one, have bugs. All I can truly attribute to Ace is that it might make a programmer's life easier when creating WoW mods, adds at least one extra folder to the AddOn for the On Demand config file, and puts green text in the AddOn window so that I know it is made with Ace. Can you please tell me why you (and others I've seen) say that Ace automatically makes it great?
And secondly, if you open AutoBarConfig.toc and find the LoadOnDemand entry, I believe if you change the ## LoadOnDemand: 1 to ## LoadOnDemand: 0 or delete it altogether, that will make it load when all the other AddOns are loaded as well. I haven't tested it myself but my primitive understanding of LUA suggests this to be how it works.
Ro is planning to integrate in Autobar ?
Thx
it may not be ace, but Tuller writes some of the cleanest code around.
The use (and reuse) of common libraries can make complex addons more easily understood, hacked and improved by other authors. Hackability is a good thing.
- Autobar had been orphaned by its original author (Saien) when he left WoW. It remained somewhat functional for several months, but it was definitely showing its age. When Toadkiller took it over, he improved it substantially and restored luster to one of the best addons ever.
My primitive understanding of LUA is clearly more primitive than yours, but that surely makes sense to me :) I'll give it a shot. Thanks.I've noticed a lot of resource use when doing things with AutoBar. One of them is during resizing buttons. My PC will freeze up for a few seconds each time they resize. 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. Hopefully you can fix it!
Thanks!
I narrowed this down more specifically. When I mouse over a button and click it, there is no lag. However, if I then click it a second time without first moving the cursor out of that button's mouse over, the UI lags up significantly. This is especially noticeable if you spam click a button (for example when it is about to come out of cooldown) and my perceived fps goes into low single digits.
[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)
---