There is an error with the LibFadingFrames when you use pet bar or stance bar,
Behaviors:
After the error appears the action bars get bugged and wont appear, you have to reload
The issue persist even if you disable the fading of the pet| stance bar but removing the bars solves it
Can only be tested with classes that have stance or pet bar (reproduced with both Paladin and Hunter), tried with DH but there was no issue since this class does not has those bars
Message: ...eUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:111: attempt to call method 'GetTexture' (a nil value)
Time: Thu Nov 30 13:59:29 2023
Count: 1
Stack: ...eUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:111: attempt to call method 'GetTexture' (a nil value)
[string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:111: in function UpdateFadeFrame' [string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:130: in functionUpdateFadeFrames'
[string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:162: in function `?'
[string "@Interface/AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua"]:55: in function <.../AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua:50>
Locals: self =
{
OnFadeFrameLeave = defined @Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:140
Enable = defined @Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:247
RegisterFrameForFading = defined @Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:172
CancelTimer = defined @Interface/AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua:147
UpdateFadeFrames = defined @Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:126
UpdateFadeFrame = defined @Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:77
SecureHookScript = defined @Interface/AddOns/AdiBags/libs/AceHook-3.0/AceHook-3.0.lua:409
TimeLeft = defined @Interface/AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua:172
To reproduce
Use AzeriteUI [5.2.132-RC] 2023-11-22
Can only be tested with classes that have stance or petbar (reproduced with both Paladin and Hunter), tried with DH but there was no issue since this does not has that bar
Expected behavior
you can use the pet | stance bar without a error window appearing
Screenshots
After closing the error message:
Additional context
Tried this on the previous version [5.2.131-RC] but the issue still persisted in Retail
Game Flavor
Dragonflight
Is there an existing issue for this?
Describe the bug
There is an error with the LibFadingFrames when you use pet bar or stance bar,
Behaviors:
Message: ...eUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:111: attempt to call method 'GetTexture' (a nil value) Time: Thu Nov 30 13:59:29 2023 Count: 1 Stack: ...eUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua:111: attempt to call method 'GetTexture' (a nil value) [string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:111: in function
UpdateFadeFrame' [string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:130: in functionUpdateFadeFrames' [string "@Interface/AddOns/AzeriteUI/Libs/LibFadingFrames-1.0/LibFadingFrames-1.0.lua"]:162: in function `?' [string "@Interface/AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua"]:55: in function <.../AddOns/DataStore/libs/AceTimer-3.0/AceTimer-3.0.lua:50>Locals: self =
To reproduce
Use AzeriteUI [5.2.132-RC] 2023-11-22 Can only be tested with classes that have stance or petbar (reproduced with both Paladin and Hunter), tried with DH but there was no issue since this does not has that bar
Expected behavior
you can use the pet | stance bar without a error window appearing
Screenshots
After closing the error message:
Additional context
Tried this on the previous version [5.2.131-RC] but the issue still persisted in Retail
The bug window says you had 3 errors, and this is the last one. I really need to see the first one that fires.
Nevermind the last comment, I was easily able to reproduce the bug. Fix coming shortly!
Fixed in 5.2.134-RC