I know it was quite a few months ago, but I'll throw this up for any future users, but for errors similar to those that shinchih2001 was having (I was trying to run ifilger as well), I found it will break if another addon is adding timers to buttons and doesn't check for tullaCC beforehand. In ifilger's case, it has it's own simple omniCC kind of thing, and it was checking for omniCC and tukUI/elvUI, but not tullaCC so they both ran. So in the end I don't think the issue is with tullaCC itself. Hopefully this helps!

I got same situation when i use IFILGER

1x tullaCC-4.3.1\cc.lua:65: attempt to index field "updater" (a nil value)
tullaCC-4.3.1\cc.lua:65: in function "SetNextUpdate"
tullaCC-4.3.1\cc.lua:90: in function "UpdateText"
tullaCC-4.3.1\cc.lua:160: in function <tullaCC\cc.lua:153>
<in C code>
FrameXML\Cooldown.lua:4: in function "CooldownFrame_SetTimer"
iFilger-3.4\ifilger-3.4.lua:227: in function <iFilger\ifilger.lua:84>
iFilger-3.4\ifilger-3.4.lua:307: in function <iFilger\ifilger.lua:262>

Locals:
self = <unnamed> {
0 = <userdata>
fontScale = 0.91666666666667
nextUpdate = 0
start = 10297.106
text = <unnamed> {}
enabled = true
duration = 60
}
remain = 60
formatStr = "|cffffffff%dm|r"
time = 1
nextUpdate = 0.5
GetTime = <func> =[C]:-1
round = <func> @tullaCC\cc.lua:22
UIParent = UIParent {
0 = <userdata>
firstTimeLoaded = 1
}
MIN_SCALE = 0.6
Timer = <table> {
UpdateText = <func> @tullaCC\cc.lua:81
Stop = <func> @tullaCC\cc.lua:73
SetNextUpdate = <func> @tullaCC\cc.lua:64
Start = <func> @tullaCC\cc.lua:153
OnSizeChanged = <func> @tullaCC\cc.lua:105
Create = <func> @tullaCC\cc.lua:125
ForceUpdate = <func> @tullaCC\cc.lua:98
}
getTimeText = <func> @tullaCC\cc.lua:43

Any chance you could implement the 'Show cooldown models' option from OmniCC? That's the only thing I'm missing to fully replace OmniCC

Edit: This seems to work, in case someone else is interested

Hello,

have downloaded the latest version and get this Error:


What shall I do? What's wrong?

Thanks for the update

So, what's happened is that in 4.3 the core UI delegates some of its ActionButton presentation management code into the C layer, and bypasses the lua API's - which is why you're not seeing the calls to SetCooldown. This is managed by the SetActionUIButton method.

Now, none of the events that would normally have triggered these activities to occur have gone anywhere, so if you're trying to track cooldown state then you should register for those events yourself (and it's recommended to register on ONE frame and dispatch to appropriate cooldowns, rather than the old action button style of having every button register for the event) and act accordingly.

There currently isn't a means to UN-register an action button, so if you need to modify the existing buttons (rather than making your own) then you'll want to do something with the cooldown frame (anchor it offscreen, or set its alpha to zero, or re-parent it onto a hidden frame) so that it doesn't show up.

I'm not sure the developers anticipated folks using some but not all of their action button rendering, so if there are specific problems that can't be solved by the suggestions above can you share them here.


^ A quote taken from your post roughly 4 hours ago.

I'm not sure if this is an issue with wow api/code that was added in 4.3 but on the ptr currently this addon does some rather wonky things. I play combat (rogue) and one of our talents decreases our cd's by 10s every time we use an offensive finisher.

Tullacc doesn't seem to be tracking this update. As in, it'll still show an ability has several (sometimes more than 1 minute) left on it when in reality it's off cd.

Kind of an odd bug but a bug nonetheless!

How to disablecooldown，just do cooldowncount.
thanks.

Meh

Oh, well thanks anyways =)

__________________

No way at all?

__________________