A small feature suggestion: To allow the user to set up a priority list in trackers based on the order in which auras are entered. This would involve checking against a boolean and if true ignore time based sorting and instead - since self.db.auras is iterated with ipairs - simply put "if auraname == self.update_name then break elseif (name == auraname) then 'do the usual stuff'... " under Tracker.prototype:UpdateAura.
This would be a nice addition until you decide whether talent scanning is bloat. (Though as Phanx has pointed out making it optional pretty much negates the concern.)
I have a question. Under individual trackers in Text options if I chose to display The time left I can then decide on Autoupdate Modes: Always Update, Update Upwards and Static. Could you explain what the 2 last ones do as regardless of what I select for Mode ( or Value for that matter ) the text behaves exactly the same ( as if it's always updating ).
I have a question. Under individual trackers in Text options if I chose to display The time left I can then decide on Autoupdate Modes: Always Update, Update Upwards and Static. Could you explain what the 2 last ones do as regardless of what I select for Mode ( or Value for that matter ) the text behaves exactly the same ( as if it's always updating ).
Autoupdate refers to the maximum (duration or stacks, whatever you have configured). It's probably easier to explain in the context of the duration spiral.
When an aura is applied, the spiral starts full and starts counting down. At each moment, the fullness of the spiral is the proportion of current-duration vs. maximum-duration. But for some abilities, the maximum-duration might change every time it's applied (i.e. combo-point based abilities). This is where Autoupdate comes in.
With "Always Update", the maximum-duration is reset every time the aura is applied, so your spiral always starts full, but might tick away faster or slower depending what the aura's actual maximum was for that application. With "Update Upwards", the maximum-duration is only increased on a new application, so over time it'll settle on the highest possible. Then, if you use a 1-combo ability, the spiral might start at halfway, but will always drain at the same speed for that ability. "Static" lets you set the correct maximum yourself.
It's even more useful for showing stacks, where you definitely don't want "Update Always" because then it would always look full (since on every aura application, it only knows how many stacks are present, not how many are possible).
For text it only comes into play if the tracker's style has text colored by relative time, in which case the color of the text depends on the current duration/stacks vs. the maximum duration/stacks. For text colored by absolute time, the maximum doesn't matter, so the autoupdate doesn't matter.
I know that's kind of convoluted; if anyone can think of a better way of explaining it, feel free. :)
I am experiencing problems when moving trackers that track abilities that are not in my spell book. The trackers that being moved tend to 'stick to' and override other already existing trackers in the window. I am using 0.3.4 beta.
I had one question, I have the addon set up pretty much how I want it, but I can't seem to get it to look like the snapshot on the dload site. I'd like to have it be just the icon with a numeric countdown, but instead i get a semi-transparent square with a numeric countdown. Any advice?
Considering that he was last active on the forums three months ago and last active on IRC 28 days ago, I think it's safe to say it isn't yet time for someone else to take over his projects.
there _are_ open tickets that wait for attention... and i'm not refering to mine from 2 days ago. Even your ticket from February has not seen any work, Phanx.
All of the open tickets are non-critical requests for new functionality, including my own. If three months without a public update to a fully functional addon meant it was time for a new developer, I wouldn't have any released addons left myself. :p
I've retired my WoW account, so I can no longer do proper development and testing of Auracle. However as Phanx noted, the existing features appear to still work just fine, and I'm happy to leave it at that for the moment.
I do still receive email updates for new tickets, so if a critical bug comes up or there is a game API change that needs to be addressed, I'll hear of it that way and do my best to keep Auracle maintained.
However, I'll need some help from you folks to do that. Anyone is welcome to develop features and send me the code changes, and show-stopping bugs I will try to research and fix myself. But in either case, I'll need help testing the changes before I tag any new releases (I did add ConfigMode though, Adirelle, since the necessary code looked pretty harmless).
Accordingly, Auracle is now available under the MIT license, so feel free to hack at it and post whatever you come up with (preferably attached to a ticket on the WoWAce project page).
I had some time today, so I tried adding stance/spec-based window visibility, which has been requested by a number of folks. Unfortunately I can't test the changes myself, so I'm looking for a few brave alpha testers.
the basics: that windows properly appear/disappear when changing specs/stances, according to the boxes checked on the window visibility options
making sure the list of available stances/shapeshifts in the window visibility options screen updates correctly when you learn new ones (which you can test by switching to and from a spec that includes an extra one)
making sure the list of auras on the window's unit is properly scanned and updated when the window first appears as a result of spec- or stance-switching
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This would be a nice addition until you decide whether talent scanning is bloat. (Though as Phanx has pointed out making it optional pretty much negates the concern.)
I have a question. Under individual trackers in Text options if I chose to display The time left I can then decide on Autoupdate Modes: Always Update, Update Upwards and Static. Could you explain what the 2 last ones do as regardless of what I select for Mode ( or Value for that matter ) the text behaves exactly the same ( as if it's always updating ).
Autoupdate refers to the maximum (duration or stacks, whatever you have configured). It's probably easier to explain in the context of the duration spiral.
When an aura is applied, the spiral starts full and starts counting down. At each moment, the fullness of the spiral is the proportion of current-duration vs. maximum-duration. But for some abilities, the maximum-duration might change every time it's applied (i.e. combo-point based abilities). This is where Autoupdate comes in.
With "Always Update", the maximum-duration is reset every time the aura is applied, so your spiral always starts full, but might tick away faster or slower depending what the aura's actual maximum was for that application. With "Update Upwards", the maximum-duration is only increased on a new application, so over time it'll settle on the highest possible. Then, if you use a 1-combo ability, the spiral might start at halfway, but will always drain at the same speed for that ability. "Static" lets you set the correct maximum yourself.
It's even more useful for showing stacks, where you definitely don't want "Update Always" because then it would always look full (since on every aura application, it only knows how many stacks are present, not how many are possible).
For text it only comes into play if the tracker's style has text colored by relative time, in which case the color of the text depends on the current duration/stacks vs. the maximum duration/stacks. For text colored by absolute time, the maximum doesn't matter, so the autoupdate doesn't matter.
I know that's kind of convoluted; if anyone can think of a better way of explaining it, feel free. :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis version should be compatible with 3.1, so feel free to give it a good testing on the PTR.
The other requests and suggestions in this thread are also on my list, I've just been busier lately. But I'll get around to it all eventually. :)
Im on a mac.
Unless you unchecked the "auto update" option for the icon, it will automatically update to the right icon the first time you see the aura.
Also, addons are not platform-specific, so it doesn't make any difference at all whether you're using a Mac, Windows, Linux, or any other OS.
I am experiencing problems when moving trackers that track abilities that are not in my spell book. The trackers that being moved tend to 'stick to' and override other already existing trackers in the window. I am using 0.3.4 beta.
I had one question, I have the addon set up pretty much how I want it, but I can't seem to get it to look like the snapshot on the dload site. I'd like to have it be just the icon with a numeric countdown, but instead i get a semi-transparent square with a numeric countdown. Any advice?
Woops, of course as soon as I post, I find it. :)
-
View User Profile
-
View Posts
-
Send Message
Project AuthorIs there some development that needs to be done? Auracle works just fine for me on a feral druid and elemental shaman.
I've retired my WoW account, so I can no longer do proper development and testing of Auracle. However as Phanx noted, the existing features appear to still work just fine, and I'm happy to leave it at that for the moment.
I do still receive email updates for new tickets, so if a critical bug comes up or there is a game API change that needs to be addressed, I'll hear of it that way and do my best to keep Auracle maintained.
However, I'll need some help from you folks to do that. Anyone is welcome to develop features and send me the code changes, and show-stopping bugs I will try to research and fix myself. But in either case, I'll need help testing the changes before I tag any new releases (I did add ConfigMode though, Adirelle, since the necessary code looked pretty harmless).
Accordingly, Auracle is now available under the MIT license, so feel free to hack at it and post whatever you come up with (preferably attached to a ticket on the WoWAce project page).
So if you're interested in this feature, please grab alpha r40 (http://static.wowace.com/uploads/18/371/676/Auracle-r40.zip) and test it for me. Some particular things to verify: