WoWInterface - 'My' ClassPower element seems to crash with '/fstack'

WoWInterface (https://www.wowinterface.com/forums/index.php)

- oUF (Otravi Unit Frames) (https://www.wowinterface.com/forums/forumdisplay.php?f=87)

- - 'My' ClassPower element seems to crash with '/fstack' (https://www.wowinterface.com/forums/showthread.php?t=56780)

'My' ClassPower element seems to crash with '/fstack'

Hi all,

I've not been touching my Class Power element and even '/fstack' for ages.

Just today I've accidentally pressed the hotkey for '/fstack' command and it gave me the following error.

Code:

2x invalid key to 'next'

[C]: in function `SetFrameStack'

...eBlizzard_DebugTools\Blizzard_DebugTools-1.0.lua:673: in function `FrameStackTooltip_Toggle'

FrameXML\ChatFrame.lua:2356: in function `?'

FrameXML\ChatFrame.lua:4734: in function `ChatEdit_ParseText'

FrameXML\ChatFrame.lua:4396: in function `ChatEdit_SendText'

FrameXML\ChatFrame.lua:2884: in function <FrameXML\ChatFrame.lua:2877>

[C]: in function `UseAction'

FrameXML\SecureTemplates.lua:345: in function `handler'

FrameXML\SecureTemplates.lua:623: in function `SecureActionButton_OnClick'

FrameXML\MultiActionBars.lua:24: in function `MultiActionButtonUp'

[string "MULTIACTIONBAR3BUTTON5"]:4: in function <[string "MULTIACTIONBAR3BUTTON5"]:1>



Locals:

(*temporary) = FrameStackTooltip {

 0 = <userdata>

 showRegions = true

 TopOverlay = <unnamed> {

 }

 showHidden = false

 default = 1

 BottomOverlay = <unnamed> {

 }

 showAnchors = true

 nextUpdate = 0

 commandKeys = <table> {

 }

}

(*temporary) = false

(*temporary) = true

(*temporary) = <unnamed> {

 0 = <userdata>

}

(*temporary) = <unnamed> {

 1 = <unnamed> {

 }

 2 = <unnamed> {

 }

 3 = <unnamed> {

 }

 4 = <unnamed> {

 }

 5 = <unnamed> {

 }

 6 = <unnamed> {

 }

 7 = <unnamed> {

 }

 8 = <unnamed> {

 }

 9 = <unnamed> {

 }

 10 = <unnamed> {

 }

 0 = <userdata>

 ClassPowerEnable = <function> defined @!MyEngine\lib\oUF\elements\classpower.lua:234

 ForceUpdate = <function> defined @!MyEngine\lib\oUF\elements\classpower.lua:229

 ClassPowerDisable = <function> defined @!MyEngine\lib\oUF\elements\classpower.lua:247

 isEnabled = true

 __max = 5

 __owner = oUF_CoG {

 }

}

(*temporary) = "5"

So, I've been debugging quite a while and found that it is causing because of my Class Power element code.

Lua Code:

-- Class Power
local classPower = CreateFrame("Frame", nil, UIParent);
classPower:SetWidth(256);
classPower:SetHeight(36);
classPower:SetPoint("CENTER");
 
for i = 1, 10 do
    local bar = CreateFrame("StatusBar", nil, classPower);
    bar:SetSize(36, 36);
 
    if i == 1 then
        bar:SetPoint("LEFT", classPower, "LEFT");
    else
        bar:SetPoint("LEFT", classPower[i - 1], "RIGHT", 3, 0);
    end
 
    classPower[i] = bar;
end
 
self.ClassPower = classPower;

I have also tested with example code provided on class power and it did not cry for such error :(

Could anyone please explain me why and how this error is occurring?

Thank you!

-- Edit #1

Basically this occurs when at least ONE class power bar (one combo point) is visible.

Give names to your bars.

Lua Code:

local classPower = CreateFrame("Frame", nil, UIParent);
classPower:SetWidth(256);
classPower:SetHeight(36);
classPower:SetPoint("CENTER");
 
for i = 1, 10 do
    local bar = CreateFrame("StatusBar", "ClassPowerBar" .. i, classPower);
    bar:SetSize(36, 36);
 
    if i == 1 then
        bar:SetPoint("LEFT", classPower, "LEFT");
    else
        bar:SetPoint("LEFT", classPower[i - 1], "RIGHT", 3, 0);
    end
 
    classPower[i] = bar;
end
 
frame.ClassPower = classPower;

In general, names aren't mandatory, but sometimes, like in this particular case, /fstack is very very picky.

-- edit #1

When you're "nesting" one frame table inside another one like so: frame[1] = anotherFrame, you must give anotherFrame a proper name, it's only needed when you index w/ numbers, if you do something like this: frame["1"] = anotherFrame, you can leave anotherFrame nameless.

Once again, it only applies to "nesting" inside other frames. For example, doing something like this won't cause any issues:

Lua Code:

local classPower = CreateFrame("Frame", nil, UIParent);
classPower:SetWidth(256);
classPower:SetHeight(36);
classPower:SetPoint("CENTER");
 
local container = {};
 
for i = 1, 10 do
    local bar = CreateFrame("StatusBar", nil, classPower);
    bar:SetSize(36, 36);
 
    if i == 1 then
        bar:SetPoint("CENTER");
    else
        bar:SetPoint("LEFT", container[i - 1], "RIGHT", 3, 0);
    end
 
    container[i] = bar;
end
 
frame.ClassPower = container;

Hi lightspark,

First of all, Thank you so much and I really appreciate your help!

I gave each of those elements a name to avoid '/fstack' crying :D

Yeap, it's definitely working :banana:

Lua Code:

-- Class Power
local classPower = CreateFrame("Frame", "$parentClassPower", self);
classPower:SetHeight(setting.height);
classPower:CustomSetPoint(setting.point);
 
for i = 1, 10 do
    local bar = CreateFrame("StatusBar", "$parentBar" .. i, classPower);
    bar:SetStatusBarTexture(LSM:Fetch("statusbar", setting.texture));
    bar:SetWidth(setting.width);
    bar:SetPoint("TOP");
    bar:SetPoint("BOTTOM");
 
    bar:SetTemplate();
    bar:SetBackground();
 
    if i == 1 then
        bar:SetPoint("LEFT");
    else
        bar:SetPoint("LEFT", classPower[i - 1], "RIGHT", 3, 0);
    end
 
    classPower[i] = bar;
end
 
classPower.UpdateColor = ClassPowerUpdateColor;
classPower.PostUpdate = ClassPowerPostUpdate;
 
self.ClassPower = classPower;

So, I do get that it's happening because of nested frames, with numeric as their key instead of string for inner frames, where inner frames do not have their unique name.

But why...?

I had a look at Blizzard_DebugTools-1.0.lua as stated on a error log, but it's totally out of my field :confused:

Quote:

Originally Posted by Lyak (Post 330458)

But why...?

I had a look at Blizzard_DebugTools-1.0.lua as stated on a error log, but it's totally out of my field :confused:

Why do you even care about it? :P

The issue is in the backend, C code, it might be a function that iterates through or does something w/ userdata, which is frame[0], but then it tries to do the same w/ unnamed frames: frame[1], frame[2], etc. It might be something else.

Sitting here and guessing is a waste of time.

Quote:

Originally Posted by lightspark (Post 330459)

Aight!

Time to proceed forward then :banana: