* Icons mia
* Support for the built in sets of macros for character (18) & general (18) as well.
* Travel macro beyond just druids: Ghost Wolf, Pally Aura & Hunter thingy.
Looks like its in Toadkiller's intent to support this, but its presently not implimented. I am keeping my eye out for this too, as I would love to be able to use my macros from Autobar.
At the risk of getting flamed by the author and moderator's I have a question.
I use about 15-20 mods and i've noticed Autobar had the highest memory usage of all of them.
It runs at approx 3.5 to 4 mb. I know thats not alot in the grand scheme of things.
I also run Pitbull(frames), Trinity 2(action bars), Tbag(bag-bank mod), Cartographer(map) and BigWigs(raid mod)
Each use about 2mb's or so during rest, solo, raid action.
Th rest of my mods run under 1mb
I'm guessing that Autobar needs to track a large list of consumables, quest, professions and thus the large memory footprint.
I currently do not use many of the many of the impressive features Autobar offers. I really use it only for basics like, mana/heal pots, food and potions/elixirs.
I've also tried the alpha versions of Autobar and did not notice any footprint difference.
Please do not misunderstand my post, Autobar is a great mod and I will continue to use it however I'm hoping i'm not the only one that would find a "stripped down" version more suited to their needs.
If you're running with embedded libraries, it's really difficult to get an accurate statistic for a mod's memory usage. Given that Autobar begins with 'A', all the other mods that use the same libraries are pulling from Autobar because that mod loads first (or before they do).
wanted to say i love using autobar for quite long now and i am happy to see the fadeout option being there now in the beta. But i have one question about the fadeout option. everytime i press CTRL or SHIFT the hidden bars show. is there any way to avoid this?
At the risk of getting flamed by the author and moderator's I have a question.
I use about 15-20 mods and i've noticed Autobar had the highest memory usage of all of them.
It runs at approx 3.5 to 4 mb. I know thats not alot in the grand scheme of things.
I also run Pitbull(frames), Trinity 2(action bars), Tbag(bag-bank mod), Cartographer(map) and BigWigs(raid mod)
Each use about 2mb's or so during rest, solo, raid action.
Th rest of my mods run under 1mb
I'm guessing that Autobar needs to track a large list of consumables, quest, professions and thus the large memory footprint.
I currently do not use many of the many of the impressive features Autobar offers. I really use it only for basics like, mana/heal pots, food and potions/elixirs.
I've also tried the alpha versions of Autobar and did not notice any footprint difference.
Please do not misunderstand my post, Autobar is a great mod and I will continue to use it however I'm hoping i'm not the only one that would find a "stripped down" version more suited to their needs.
Ah yes, the topic that wont die. Perhaps I should rename it X-Bar, then some other Ace mod could get the blame. But that would be disingenuous. So here is a new tac on it which I will add to http://code.google.com/p/autobar/wiki/FAQ.
First let us run Fubar + PerformanceFu because we are lazy and want to just see whats what.
690 k Fubar
776 k PerformanceFu
= 1.4 MB
Next Autobar is added.
690 k Fubar
346 k PerformanceFu
3.49 M AutoBar
= 4.5 MB
So AutoBar directly causes about 3.1 MB of memory use.
Now notice that 430k shifted from PerformanceFu to AutoBar. So 430k worth of libraries are shared between these 3 mods. If you only use these 3 mods then 3.1 MB is what it costs to run AutoBar. However if you use other Ace mods, then there is an opportunity to share libraries between more mods. The true cost of library can thus be viewed as its raw size & blamed on one addon, or more ideally it is shared & blamed amongst all using mods. This second view is not what you get though. Instead you get libs assigned to the first loaded mod that uses them.
Now any way you slice it, 3.1 is rather large. You can disembed the respective libraries which will give you a look at what each contributes to memory usage. I will do that next time I run out of code to write. The last time I checked it was about 300-600k for AutoBar. If someone that runs disembeded could post some numbers I can add them to this post & the FAQ.
What can AutoBar do to be more efficient though?
1) Well, on the todo list is getting rid of LibBabbleSpell which is mostly obsolete now that blizzard has a better API for spell info. Thats about 60k or so, estimated from localized file size.
2) Spin out AutoBar specific PT3 sets. This requires a bit of PT3 work, but for instance AutoBar uses only a small fraction of the included PT3 sets. That would probably drop PT3 from around 300k to say 100k. Of course, 3.1 is also not compressed like 3.0 used to be so theres that as well.
3) Only instantiate used categories & thus their PT3 sets.
4) Switch to leaner Base Libraries. So Rock or Ace3.
Toady, any input on the macro question last page? :)
Also additionally, I'm not sure if this is a wow limitation or what, but is there some way to show actual "charges left" of drums if they're in Autobar?
Toady, any input on the macro question last page? :)
...
Also additionally, I'm not sure if this is a wow limitation or what, but is there some way to show actual "charges left" of drums if they're in Autobar?
Like Lewzephyr noted, I'll work on macros some more after beta.
Blizzard has narrowed the choices here for how you specify an "item" type button. They are obsoleting bag & slot as attributes for type "item", but it seems that you can directly specify <bag>.." "..<slot> instead of an itemLink. Currently AutoBar has switched to using itemLink, as this functions like use by name: Once you run out of items in a particular slot, it then uses the next slot etc. This fixes the issue in boss fights where u cant use the potion again once its first slot is empty.
Similarly that is how the item is specified for the tooltip. Unfortunately the tooltip is too retarded to pick an item & report its charges, or even do the smart thing and pick the item it would use if clicked on & report its charges. Instead it just straight up lies. In either case the supplied API code ends up using the first item not the least charge item. ugh. As for figuring out the charges manually, I need to find some sample code that does that. I think someone linked some a while ago.
...wanted to say i love using autobar for quite long now and i am happy to see the fadeout option being there now in the beta. But i have one question about the fadeout option. everytime i press CTRL or SHIFT the hidden bars show. is there any way to avoid this?
Like Lewzephyr noted, I'll work on macros some more after beta.
Blizzard has narrowed the choices here for how you specify an "item" type button. They are obsoleting bag & slot as attributes for type "item", but it seems that you can directly specify <bag>.." "..<slot> instead of an itemLink.
Thanks a lot for the reply :)
Curious about this however:
Quote from Toadkiller »
Currently AutoBar has switched to using itemLink, as this functions like use by name: Once you run out of items in a particular slot, it then uses the next slot etc. This fixes the issue in boss fights where u cant use the potion again once its first slot is empty.
This has still been happening. Say I have 6 mana potions, it uses one, then when it needs to start on the new stack, it will simply not work. This is usually the case in boss fights.
Does it require me to get out of combat in between?
...This has still been happening. Say I have 6 mana potions, it uses one, then when it needs to start on the new stack, it will simply not work. This is usually the case in boss fights...
At long last the "my AutoBar does not update because I disabled it" issue has been identified and fixed. The google documentation now refers to the Alpha. Rewrote the crufty category code & imported & upgraded old custom category data. You should be able to rename categories without issues now, and "." is no longer acceptable as part of a category name & will be automatically removed.
2.04.01.42 alpha
-- Documentation for the Alpha is now on http://code.google.com/p/autobar
-- Set AutoBar to active if it is not.
-- Add additional porting items to Hearth. BT attunement, Legendary Staff kara.
-- Fix custom Categories to be keyed not indexed
-- lanatha: Fix AutoBar.Class.Button.prototype:GetIconTexture() for "showEmptyButtons" or "alwaysShow"
--- Outstanding Alpha Issues
--- Fix sharing for barButtons / Buttons
--- Reset Button for built in Bars
--- Reset Button for built in Buttons
--- Reset Button for AutoBar
--- Resolve issues with class buttons being placed on account bars.
--- Implement upgrade to version 1: delete old data.
Ah yes, the topic that wont die. Perhaps I should rename it X-Bar, then some other Ace mod could get the blame. But that would be disingenuous. So here is a new tac on it which I will add to http://code.google.com/p/autobar/wiki/FAQ.
First let us run Fubar + PerformanceFu because we are lazy and want to just see whats what.
690 k Fubar
776 k PerformanceFu
= 1.4 MB
Next Autobar is added.
690 k Fubar
346 k PerformanceFu
3.49 M AutoBar
= 4.5 MB
So AutoBar directly causes about 3.1 MB of memory use.
Now notice that 430k shifted from PerformanceFu to AutoBar. So 430k worth of libraries are shared between these 3 mods. If you only use these 3 mods then 3.1 MB is what it costs to run AutoBar. However if you use other Ace mods, then there is an opportunity to share libraries between more mods. The true cost of library can thus be viewed as its raw size & blamed on one addon, or more ideally it is shared & blamed amongst all using mods. This second view is not what you get though. Instead you get libs assigned to the first loaded mod that uses them.
Now any way you slice it, 3.1 is rather large. You can disembed the respective libraries which will give you a look at what each contributes to memory usage. I will do that next time I run out of code to write. The last time I checked it was about 300-600k for AutoBar. If someone that runs disembeded could post some numbers I can add them to this post & the FAQ.
What can AutoBar do to be more efficient though?
1) Well, on the todo list is getting rid of LibBabbleSpell which is mostly obsolete now that blizzard has a better API for spell info. Thats about 60k or so, estimated from localized file size.
2) Spin out AutoBar specific PT3 sets. This requires a bit of PT3 work, but for instance AutoBar uses only a small fraction of the included PT3 sets. That would probably drop PT3 from around 300k to say 100k. Of course, 3.1 is also not compressed like 3.0 used to be so theres that as well.
3) Only instantiate used categories & thus their PT3 sets.
4) Switch to leaner Base Libraries. So Rock or Ace3.
Heres a screenie of performancefu when running autobar dissembeded.
(Cropped down my very LONG list a bit to make it easier to post.)
This has still been happening. Say I have 6 mana potions, it uses one, then when it needs to start on the new stack, it will simply not work. This is usually the case in boss fights.
Does it require me to get out of combat in between?
That is very lightly, a workaround thou would be using mana injectors instead, then u have a stack of 20 instead (and it saves bagspace to boot).
hey, which LibPeriodicTable-3.1 contains quest items and is there an easy way to modify it? I will create a ticket for the missing items, but in the mean time I'd like to add the ones I use everyday.
Ah yes, the topic that wont die. Perhaps I should rename it X-Bar, then some other Ace mod could get the blame. But that would be disingenuous. So here is a new tac on it which I will add to http://code.google.com/p/autobar/wiki/FAQ.
First let us run Fubar + PerformanceFu because we are lazy and want to just see whats what.
690 k Fubar
776 k PerformanceFu
= 1.4 MB
Next Autobar is added.
690 k Fubar
346 k PerformanceFu
3.49 M AutoBar
= 4.5 MB
So AutoBar directly causes about 3.1 MB of memory use.
Now notice that 430k shifted from PerformanceFu to AutoBar. So 430k worth of libraries are shared between these 3 mods. If you only use these 3 mods then 3.1 MB is what it costs to run AutoBar. However if you use other Ace mods, then there is an opportunity to share libraries between more mods. The true cost of library can thus be viewed as its raw size & blamed on one addon, or more ideally it is shared & blamed amongst all using mods. This second view is not what you get though. Instead you get libs assigned to the first loaded mod that uses them.
Now any way you slice it, 3.1 is rather large. You can disembed the respective libraries which will give you a look at what each contributes to memory usage. I will do that next time I run out of code to write. The last time I checked it was about 300-600k for AutoBar. If someone that runs disembeded could post some numbers I can add them to this post & the FAQ.
What can AutoBar do to be more efficient though?
1) Well, on the todo list is getting rid of LibBabbleSpell which is mostly obsolete now that blizzard has a better API for spell info. Thats about 60k or so, estimated from localized file size.
2) Spin out AutoBar specific PT3 sets. This requires a bit of PT3 work, but for instance AutoBar uses only a small fraction of the included PT3 sets. That would probably drop PT3 from around 300k to say 100k. Of course, 3.1 is also not compressed like 3.0 used to be so theres that as well.
3) Only instantiate used categories & thus their PT3 sets.
4) Switch to leaner Base Libraries. So Rock or Ace3.
I appreciate the response. I've bookmarked your wiki page so in the future I will look there before posting.
Looks like its in Toadkiller's intent to support this, but its presently not implimented. I am keeping my eye out for this too, as I would love to be able to use my macros from Autobar.
I use about 15-20 mods and i've noticed Autobar had the highest memory usage of all of them.
It runs at approx 3.5 to 4 mb. I know thats not alot in the grand scheme of things.
I also run Pitbull(frames), Trinity 2(action bars), Tbag(bag-bank mod), Cartographer(map) and BigWigs(raid mod)
Each use about 2mb's or so during rest, solo, raid action.
Th rest of my mods run under 1mb
I'm guessing that Autobar needs to track a large list of consumables, quest, professions and thus the large memory footprint.
I currently do not use many of the many of the impressive features Autobar offers. I really use it only for basics like, mana/heal pots, food and potions/elixirs.
I've also tried the alpha versions of Autobar and did not notice any footprint difference.
Please do not misunderstand my post, Autobar is a great mod and I will continue to use it however I'm hoping i'm not the only one that would find a "stripped down" version more suited to their needs.
wanted to say i love using autobar for quite long now and i am happy to see the fadeout option being there now in the beta. But i have one question about the fadeout option. everytime i press CTRL or SHIFT the hidden bars show. is there any way to avoid this?
Ah yes, the topic that wont die. Perhaps I should rename it X-Bar, then some other Ace mod could get the blame. But that would be disingenuous. So here is a new tac on it which I will add to http://code.google.com/p/autobar/wiki/FAQ.
First let us run Fubar + PerformanceFu because we are lazy and want to just see whats what.
690 k Fubar
776 k PerformanceFu
= 1.4 MB
Next Autobar is added.
690 k Fubar
346 k PerformanceFu
3.49 M AutoBar
= 4.5 MB
So AutoBar directly causes about 3.1 MB of memory use.
Now notice that 430k shifted from PerformanceFu to AutoBar. So 430k worth of libraries are shared between these 3 mods. If you only use these 3 mods then 3.1 MB is what it costs to run AutoBar. However if you use other Ace mods, then there is an opportunity to share libraries between more mods. The true cost of library can thus be viewed as its raw size & blamed on one addon, or more ideally it is shared & blamed amongst all using mods. This second view is not what you get though. Instead you get libs assigned to the first loaded mod that uses them.
Now any way you slice it, 3.1 is rather large. You can disembed the respective libraries which will give you a look at what each contributes to memory usage. I will do that next time I run out of code to write. The last time I checked it was about 300-600k for AutoBar. If someone that runs disembeded could post some numbers I can add them to this post & the FAQ.
What can AutoBar do to be more efficient though?
1) Well, on the todo list is getting rid of LibBabbleSpell which is mostly obsolete now that blizzard has a better API for spell info. Thats about 60k or so, estimated from localized file size.
2) Spin out AutoBar specific PT3 sets. This requires a bit of PT3 work, but for instance AutoBar uses only a small fraction of the included PT3 sets. That would probably drop PT3 from around 300k to say 100k. Of course, 3.1 is also not compressed like 3.0 used to be so theres that as well.
3) Only instantiate used categories & thus their PT3 sets.
4) Switch to leaner Base Libraries. So Rock or Ace3.
Also additionally, I'm not sure if this is a wow limitation or what, but is there some way to show actual "charges left" of drums if they're in Autobar?
Thanks.
Like Lewzephyr noted, I'll work on macros some more after beta.
Blizzard has narrowed the choices here for how you specify an "item" type button. They are obsoleting bag & slot as attributes for type "item", but it seems that you can directly specify <bag>.." "..<slot> instead of an itemLink. Currently AutoBar has switched to using itemLink, as this functions like use by name: Once you run out of items in a particular slot, it then uses the next slot etc. This fixes the issue in boss fights where u cant use the potion again once its first slot is empty.
Similarly that is how the item is specified for the tooltip. Unfortunately the tooltip is too retarded to pick an item & report its charges, or even do the smart thing and pick the item it would use if clicked on & report its charges. Instead it just straight up lies. In either case the supplied API code ends up using the first item not the least charge item. ugh. As for figuring out the charges manually, I need to find some sample code that does that. I think someone linked some a while ago.
Anyway, again, not till after the beta.
I will add more fadeOut control after beta.
Thanks a lot for the reply :)
Curious about this however:
This has still been happening. Say I have 6 mana potions, it uses one, then when it needs to start on the new stack, it will simply not work. This is usually the case in boss fights.
Does it require me to get out of combat in between?
So you are not using the Alpha?
At long last the "my AutoBar does not update because I disabled it" issue has been identified and fixed. The google documentation now refers to the Alpha. Rewrote the crufty category code & imported & upgraded old custom category data. You should be able to rename categories without issues now, and "." is no longer acceptable as part of a category name & will be automatically removed.
Alpha: http://code.google.com/p/autobar/downloads
Report missing items: http://code.google.com/p/autobar/issues/list?q=label%3AMissingItem&can=1
Report issues and find Alpha documentation & FAQ here: http://code.google.com/p/autobar
2.04.01.42 alpha
-- Documentation for the Alpha is now on http://code.google.com/p/autobar
-- Set AutoBar to active if it is not.
-- Add additional porting items to Hearth. BT attunement, Legendary Staff kara.
-- Fix custom Categories to be keyed not indexed
-- lanatha: Fix AutoBar.Class.Button.prototype:GetIconTexture() for "showEmptyButtons" or "alwaysShow"
--- Outstanding Alpha Issues
--- Fix sharing for barButtons / Buttons
--- Reset Button for built in Bars
--- Reset Button for built in Buttons
--- Reset Button for AutoBar
--- Resolve issues with class buttons being placed on account bars.
--- Implement upgrade to version 1: delete old data.
Heres a screenie of performancefu when running autobar dissembeded.
(Cropped down my very LONG list a bit to make it easier to post.)
That is very lightly, a workaround thou would be using mana injectors instead, then u have a stack of 20 instead (and it saves bagspace to boot).
I appreciate the response. I've bookmarked your wiki page so in the future I will look there before posting.
WTB Fel Mana Potion Injectors :)