Authors CurseForge

I don't suppose this addon will work with filters such as "dispelable" or "curable" for both buffs and debuffs?

The version tagged as beta has the same bug that HunterZ got.

[2009/02/10 20:38:35-400-x1]: Auracle-0.3\Tracker.lua:639: attempt to index local 'dbtt' (a nil value)
Auracle-0.3\Tracker.lua:235: in function <Interface\AddOns\Auracle\Tracker.lua:190>
(tail call): ?:
Auracle-0.3\Window.lua:141: in function <Interface\AddOns\Auracle\Window.lua:110>
(tail call): ?:
Auracle-0.3\Auracle.lua:408: in function `Startup'
Auracle-0.3\Auracle.lua:157: in function <Interface\AddOns\Auracle\Auracle.lua:156>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):496: in function `EnableAddon'
AceAddon-3.0-5 (Ace3):589: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:575>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:229: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:252: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:414: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---

Edit: Might help if I pasted the right error ...

Quote from Scae

The version tagged as beta has the same bug that HunterZ got.

Grr, another stupid mistake. Forgot that integer 0 still evaluates as true in Lua.

Try r27. If that one works then I'll tag it 0.3.2.

with r27.

[2009/02/10 23:11:55-402-x1]: Auracle-0.3\Tracker.lua:646: attempt to index local 'dbtt' (a nil value)
Auracle-0.3\Tracker.lua:236: in function <Interface\AddOns\Auracle\Tracker.lua:191>
(tail call): ?:
Auracle-0.3\Window.lua:142: in function <Interface\AddOns\Auracle\Window.lua:111>
(tail call): ?:
Auracle-0.3\Auracle.lua:406: in function `Startup'
Auracle-0.3\Auracle.lua:155: in function <Interface\AddOns\Auracle\Auracle.lua:154>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):496: in function `EnableAddon'
AceAddon-3.0-5 (Ace3):589: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:575>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:229: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:252: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:414: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---

Please try r28. Crossing my fingers..

[2009/02/10 23:32:33-406-x1]: Auracle-0.3\Auracle.lua:458: attempt to index field 'background' (a nil value)
Auracle-0.3\Auracle.lua:384: in function `Startup'
Auracle-0.3\Auracle.lua:155: in function <Interface\AddOns\Auracle\Auracle.lua:154>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):496: in function `EnableAddon'
AceAddon-3.0-5 (Ace3):589: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:575>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:229: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:252: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:414: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

Nope, sorry. Might be simpler for me to delete my saved vars and start again :)

Quote from Scae

Nope, sorry. Might be simpler for me to delete my saved vars and start again :)

I haven't had a chance to try the newer versions on my Paladin (who had the error), but I did notice that my Hunter had no problems with Auracle because I didn't start using it on that toon until after this issue started. Therefore, resetting your savedvariables may be a viable workaround.

Quote from HunterZ

I haven't had a chance to try the newer versions on my Paladin (who had the error), but I did notice that my Hunter had no problems with Auracle because I didn't start using it on that toon until after this issue started. Therefore, resetting your savedvariables may be a viable workaround.

Yeah, the bug is caused by the code that tried to upgrade the saved variables format between 0.2.3 and 0.3.0, so anyone who first installed after 0.3.0 is unaffected.

But I'd still prefer not to make all the early testers redo their whole configs unless necessary. :)

To that end, I've made another tweak -- if you've ever had this error, try r29.

I've tagged 0.3.2, which (again) hopefully fixes the saved vars issue for 0.2.3 users. Also:

• fixed a bug that caused changes to window visibility by group and combat status to not take effect immediately
• window styles may now set scale and opacity, which will be inherited by trackers
• windows may now set visibility based on instance type (none,battleground,arena,5man,raid)
• tweaked "Always Update" for maximum stacks to only update on a new application of the aura (not, for example, charges being consumed without re-applying)

Yay! It's loads without errors!... so now I have another bug for you :D

This ones a bit strange. I managed to disable the spirals as you said a few posts ago (yeah, how'd I miss that options :S). But when choosing fonts I generated the error below (twice) and the cooldowns/stacks wouldn't show.
However, after fiddling with the spiral options and changing the fonts about a bit it starting working.

So now I have no spirals, I do have cooldowns (with changable fonts). Which is exactly how I wanted it. Good work! :)

[2009/02/11 18:56:49-407-x1]: Auracle-0.3\Tracker.lua:603: <unnamed>:SetText(): Font not set
Auracle-0.3\Tracker.lua:603: in function `?'
Auracle-0.3\TrackerStyle.lua:167: in function `Apply'
Auracle-0.3\TrackerStyle.lua:664: in function <Interface\AddOns\Auracle\TrackerStyle.lua:662>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0-25:782: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:601>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-16 (Ace3):267: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47>:

---

P.S. Did you know disabling a spiral also blocks the external cooldown mod, although I guess there's not much you can do about that.

Quote from Scae

Yay! It's loads without errors!... so now I have another bug for you :D

This ones a bit strange. I managed to disable the spirals as you said a few posts ago (yeah, how'd I miss that options :S). But when choosing fonts I generated the error below (twice) and the cooldowns/stacks wouldn't show.
However, after fiddling with the spiral options and changing the fonts about a bit it starting working.

So now I have no spirals, I do have cooldowns (with changable fonts). Which is exactly how I wanted it. Good work! :)



P.S. Did you know disabling a spiral also blocks the external cooldown mod, although I guess there's not much you can do about that.

Yay! Glad to finally have that bug quashed.

There used to be a bug where setting font size to 0 (both relative and static) caused an error like that, because the game doesn't actually allow fonts to be size 0. I thought I fixed that by making fonts use a minimum effective size of 1, but your bug looks an awful lot like that previous one.

So that leads me to think the font is not initializing for some other reason -- for example, if it had an invalid font string. I didn't think that would be possible since it implies that LibSharedMedia is advertising fonts that aren't actually available, but that's my best guess.

Can you nail down what exact settings (especially font, outline and sizes) produce that bug?

As far as I know, every standalone/external cooldown count mod works by hooking onto the "cooldown spiral" graphic layer and printing text based on its progress. So if there's no cooldown spiral, I'm not surprised that there's no external count either.

Feature request: add offset options for the text. Currently, if I make the text large enough to read at a glance (which, after all, is the whole point) it becomes somewhat difficult to see the icon behind the text. An way to move the text to the bottom/top of (or even just below/above) the icon would be great.

Well I played about with all sorts of text/spiral settings to no avail. I cannot reproduce that bug.
I can only assume it was something to do with having no font defined from the last time I used auracle, as last time I think i had an invalid font path (when paths were used) which I never got round to fixing.


I've noticed on one of my chars the first window I set (target debuffs in this case) forgets that I set it to not show when out of combat. The rest of the windows seem to remember their settings.

Quote from Scae

Well I played about with all sorts of text/spiral settings to no avail. I cannot reproduce that bug.
I can only assume it was something to do with having no font defined from the last time I used auracle, as last time I think i had an invalid font path (when paths were used) which I never got round to fixing.

That makes sense; when I moved to LSM I didn't put in a check to validate any old settings. Maybe I should do that, in case someone selects a border/background/font and then removes the addon that provided it (and registered it via LSM).

Quote from Scae

I've noticed on one of my chars the first window I set (target debuffs in this case) forgets that I set it to not show when out of combat. The rest of the windows seem to remember their settings.

Odd. The combat visibility didn't work right until 0.3.2 I think, but it should at least remember what you set it to. Did it just forget once (like when you upgraded), or does it happen repeatedly on every UI reload?

Every time the UI loads I have to untick the option for 'out of combat'. What's weird is it only applies to that window. I have 4 windows on that char and 2 more on another char, all of which work fine the the 'out of combat' (and other) visibility options.

Quote from Scae

Every time the UI loads I have to untick the option for 'out of combat'. What's weird is it only applies to that window. I have 4 windows on that char and 2 more on another char, all of which work fine the the 'out of combat' (and other) visibility options.

This appears to be caused by a bug in AceDB's handling of default values for boolean table keys. I've worked around it by switching to manual defaults handling; try r32.

Heya

I was wondering if you would consider adding cooldowns as well. I am used TellMEWhen poping Tiger's Fury when its CD wears off and I kind of miss it when I switch to Auracle as my aura tracker :)

Cooldowns are not really within the scope of a compact custom aura monitor... there are plenty of standalone cooldown monitor addons that will work just fine with Auracle. Please use one of them, instead of promoting bloat and feature creep!

[2009/02/13 14:08:37-6593-x1]: Auracle-0.3\Window.lua:331: attempt to index field 'plrInstance' (a nil value)
Auracle-0.3\Window.lua:163: in function <Interface\AddOns\Auracle\Window.lua:124>
(tail call): ?:
Auracle-0.3\Auracle.lua:413: in function `Startup'
Auracle-0.3\Auracle.lua:155: in function <Interface\AddOns\Auracle\Auracle.lua:154>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):496: in function `EnableAddon'
AceAddon-3.0-5 (Ace3):589: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:575>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:229: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:252: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:414: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---

One of my two Windows Loads on startup, but doesnt change when an aura is active. I cant even enter the options because only an empty window shows up.