Texture:SetTexCoord() is not working for texture of Health StatusBar created via oUF

Layback_ · 03-04-16, 07:31 PM

So, I've been posting this on "Graphics Help" forum and came back here as I'm guessing that my issue is related to oUF.

First of all, here's lines of code that I wrote to create Health bar:

Lua Code:

local LSM = LibStub("LibSharedMedia-3.0");
 
local HEALTH_BAR = LSM:Fetch("statusbar", "fer10");
 
A.CreateHealthBar = function(f, unit)
    local Health = CreateFrame("StatusBar", f:GetName() .. "HealthBar", f);
    Health:SetFrameStrata("LOW");
    Health:SetStatusBarTexture(HEALTH_BAR);
    Health:SetStatusBarColor(0.69, 0.69, 0.69, 1);
 
    if (unit == "player" or unit == "target") then
        Health:SetSize(f:GetWidth() - 82, f:GetHeight() - 38);
 
        if (unit == "player") then
            Health:SetPoint("TOPRIGHT", f, "TOPRIGHT", -1, -1);
        elseif (unit == "target") then
            Health:SetPoint("TOPLEFT", f, "TOPLEFT", 1, -1);
            Health:SetReverseFill(true);
            Health:GetStatusBarTexture():SetTexCoord(1, 0, 0, 1);
        end
    end
    
    ...
end

So, I utilized Texture:SetTexCoord() to simply flip the status bar along the axis if the unit is a "target" and "Health:GetStatusBarTexture():SetTexCoord(1, 0, 0, 1);" did not work at all...

Well... it could be working but something inside oUF module must be updating it again after its initialization, so that it actually goes back to its original state.

The reason that I made this assumption is because the following lines of code worked perfectly outside oUF:

Lua Code:

local LSM = LibStub("LibSharedMedia-3.0");
 
local BAR = LSM:Fetch("statusbar", "fer10");
 
local testbar = CreateFrame("StatusBar", nil, UIParent);
testbar:SetSize(248, 40);
testbar:SetPoint("CENTER");
testbar:SetStatusBarTexture(BAR);
testbar:GetStatusBarTexture():SetTexCoord(1, 0, 0, 1);

So for the testing, inside "health.lua" module, I actually added "health:GetStatusBarTexture():SetTexCoord(1, 0, 0, 1);" before/after "health.PostUpdate" (inside Update function) is called and it performed some kind of ugly animation

...

Could anyone please tell me how I could achieve my object without destroying the things.

zork · 03-05-16, 06:45 AM

Ok I tried my best to explain it to you in the other thread but I seem to have failed.

I created an addon for you: oUF_Doom.

https://github.com/zorker/rothui/tre...ow6.0/oUF_Doom

Screenshots: http://imgur.com/a/BHfcs

It does exactly what I described in the other thread. Create a fake statusbar for value updates.
Create a texture and apply the value changes via SetTexCoord to that texture.

Layback_ · 03-05-16, 06:19 PM

Originally Posted by zork

Ok I tried my best to explain it to you in the other thread but I seem to have failed.

I created an addon for you: oUF_Doom.

https://github.com/zorker/rothui/tre...ow6.0/oUF_Doom

Screenshots: http://imgur.com/a/BHfcs

It does exactly what I described in the other thread. Create a fake statusbar for value updates.
Create a texture and apply the value changes via SetTexCoord to that texture.

Mmmmmmmmm.....

I don't know why that is not working for me..............

Like I mentioned it works fine outside oUF, but not working within functions that I created for oUF D:.........

Maybe I should give it an another try.

P.S: I know you tried your best to explain as much as you know, and I really and really appreciate your help.

Layback_ · 03-07-16, 05:39 PM

Originally Posted by zork

Ok I tried my best to explain it to you in the other thread but I seem to have failed.

I created an addon for you: oUF_Doom.

https://github.com/zorker/rothui/tre...ow6.0/oUF_Doom

Screenshots: http://imgur.com/a/BHfcs

It does exactly what I described in the other thread. Create a fake statusbar for value updates.
Create a texture and apply the value changes via SetTexCoord to that texture.

Hi zork,

before I go further, I guess I need some clarifications regarding PreUpdate and PostUpdate.

Could I get some explanations regarding them?

zork · 03-09-16, 06:00 PM

oUF handles element events for you (like UNIT_HEALTH, UNIT_POWER etc.). If one fires oUF runs its UpdateHealth or UpdatePower function. That will update any element you created of that type. Sometimes you want to hook that event. This the case in this example since we are using the statusbar for value updates only. The real visible statusbar is a texture.

Layback_ · 03-10-16, 03:42 PM

Originally Posted by zork

oUF handles element events for you (like UNIT_HEALTH, UNIT_POWER etc.). If one fires oUF runs its UpdateHealth or UpdatePower function. That will update any element you created of that type. Sometimes you want to hook that event. This the case in this example since we are using the statusbar for value updates only. The real visible statusbar is a texture.

So, do PreUpdate and PostUpdate have a different call time?

I understand that they are called based on events, but...

EDIT: Sorry for keep asking... I'm just way too stupid to understand things at once...

zork · 03-11-16, 06:52 AM

PreUpdate and PostUpdate do excactly what you would think they do. The first one is called before the update function runs. The latter runs after the update function is done.

Power PreUpdate call
https://github.com/haste/oUF/blob/ma...power.lua#L130

Power PostUpdate call
https://github.com/haste/oUF/blob/ma...power.lua#L196

Try reading through oUF/elements and to get a better understanding how each element works.

Layback_ · 03-11-16, 09:59 PM

Originally Posted by zork

PreUpdate and PostUpdate do excactly what you would think they do. The first one is called before the update function runs. The latter runs after the update function is done.

Power PreUpdate call
https://github.com/haste/oUF/blob/ma...power.lua#L130

Power PostUpdate call
https://github.com/haste/oUF/blob/ma...power.lua#L196

Try reading through oUF/elements and to get a better understanding how each element works.

Yeah, I've seen those structures (PreUpdate - some codes - PostUpdate) from most of oUF elements.

So, where could I find the definition of PreUpdate and PostUpdate function?

I've been searching for their function definition inside oUF and could've not found any (as there were only function calls)

...

Also, I have dumped PostUpdate of my power bar (e.g: /dump oUF_PlayerFrame.Power.PostUpdate) and it returned nil.

Do they act as an placeholder until I actually set some functions to them like what you have done on your oUF_Doom (e.g: self.Health.PostUpdate = UpdateHealth)?

Sorry for keep asking things...

EDIT: I have utilized your oUF_Doom codes and tried to create something similar (without making fake health bar actually)

Lua Code:

A.CreateHealthBar = function(f, unit)
    local Health = CreateFrame("StatusBar", f:GetName() .. "HealthBar", f);
    Health:SetFrameStrata("LOW");
    Health:SetStatusBarTexture(HEALTH_BAR);
    Health:SetStatusBarColor(0.69, 0.69, 0.69, 1);
 
    if (unit == "player" or unit == "target") then
        Health:SetSize(f:GetWidth() - 67, f:GetHeight() - 30);
 
        if (unit == "player") then
            Health:SetPoint("TOPRIGHT", f, "TOPRIGHT", -1, -1);
        elseif (unit == "target") then
            Health:SetPoint("TOPLEFT", f, "TOPLEFT", 1, -1);
 
            Health.PostUpdate = A.PostUpdateHealth;
        end
    end
 
    local backdrop = CreateFrame("Frame", nil, Health);
    backdrop:SetSize(Health:GetWidth() + 2, Health:GetHeight() + 2);
    backdrop:SetPoint("CENTER");
    backdrop:SetBackdrop({
        bgFile = nil,
        edgeFile = BACKDROP,
        edgeSize = 1,
        insets = {
            left = 1,
            right = 1,
            top = 1,
            bottom = 1,
        },
    });
    backdrop:SetBackdropBorderColor(0, 0, 0, 1);
 
    Health.backdrop = backdrop;
 
    Health.bg = Health:CreateTexture(nil, "BACKGROUND");
    Health.bg:SetAllPoints(true);
    Health.bg:SetTexture(BACKDROP);
    Health.bg:SetVertexColor(0.05, 0.05, 0.05, 1);
 
    f.Health = Health;
    f.Health.bg = Health.bg;
end
 
A.PostUpdateHealth = function(self, unit)
    local hmin,hmax = self:GetMinMaxValues();
    local hcur = self:GetValue();
    local hcurp = hcur / hmax or 0;
 
    local ULx, ULy, LLx, LLy, URx, URy, LRx, LRy = 0, 0, 0, 1, hcurp, 0, hcurp, 1;
 
    self:GetStatusBarTexture():SetTexCoord(URx,URy, LRx,LRy, ULx,ULy, LLx,LLy);
end
 
C.styles["target"] = function(f, unit)
    A.CreateHealthBar(f, unit);
end
 
C.stylemanager = function(f, unit)
    if C.styles[unit] then
        C.styles[unit](f, unit);
    end
end
 
YUF:RegisterStyle("YUF_Style", C.stylemanager);
 
YUF:Spawn("target", "YUI_Target");

where A and C are elements of AddonTable.

So, in my case, SetTexCoord works only when I select target - deselect - select same target again.

And when it gets to update status bar (like when status bar's value changes), the texture goes back to original coordinate points...

(P.S: I just used oUF's default 'health' element)

zork · 03-12-16, 12:23 PM

I think you are correct on that. Applying SetTexCoord to a statusbar texture is not working. You need that extra texture.

Layback_ · 03-12-16, 07:43 PM

Originally Posted by zork

I think you are correct on that. Applying SetTexCoord to a statusbar texture is not working. You need that extra texture.

damn............................................................

another texture QQ.........................................

Do you reckon that's the problem with WoW API or something wrong with internal siad of oUF?

zork · 03-14-16, 03:29 AM

Well you could just create a statusbar on your own and test it.

Lua Code:

local p = CreateFrame("StatusBar",nil,UIParent)
p:SetSize(256,32)
p:SetPoint("CENTER")
p:SetStatusBarTexture("myTexture")
p:RegisterUnitEvent("UNIT_POWER","player")
 
local function OnEvent(self,event,unit,...)
  local pc, pm = UnitPower(unit), UnitPowerMax(unit)
  self:SetMinMaxValues(0,pm)
  self:SetValue(pc)
  print(...)
end
 
p:HookScript("OnEvent",OnEvent)

Folji · 03-19-16, 05:29 AM

Decided to try and test this, see how it'd go.

Lua Code:

lib.CreateHealth = function(frame,frametype,width,height,point,x,y)
 
    local hp = CreateFrame('StatusBar',nil,frame)
    hp:SetSize(width,height)
    hp:SetPoint(point,frame,x,y)
    hp:SetStatusBarTexture('Interface\\AddOns\\TestUI\\media\\playerhp')
    hp:SetStatusBarColor(0,1,0)
    hp:RegisterUnitEvent('UNIT_HEALTH', frametype)
 
    if (frametype == 'target') then
        hp:SetReverseFill(true)
        hp:GetStatusBarTexture():SetTexCoord(1,0,0,1)
        hp:GetStatusBarTexture():SetPoint('RIGHT', hp)
    end
 
    local function HealthUpdate()
        local hpcur, hpmax = UnitHealth(frametype), UnitHealthMax(frametype)
        hp:SetMinMaxValues(0,hpmax)
        hp:SetValue(hpcur)
    end
 
    hp:HookScript("OnEvent",HealthUpdate)
 
    local function CheckCoords()
        print(frametype.." : "..hp:GetStatusBarTexture():GetPoint())
        print(hp:GetStatusBarTexture():GetTexCoord())
 
    end
 
    frame:HookScript('OnMouseUp',CheckCoords)
end

Seems like not being able to use hp:GetStatusBarTexture():SetTexCoord(1,0,0,1) to flip the texture is largely down to how the game handles statusbars? I don't know if I'm writing something wrong here or what, but testing around with it showed me that the statusbars were narrowing by changing the TexCoords directly. So no matter what it was set to before, it'd change back to 0,1,0,1 and then gradually drop down from there.

GetStatusBarTexture():GetPoint() defaulted to TOPLEFT, and trying to SetPoint() did absolutely nothing.

Layback_ · 03-20-16, 06:17 PM

Originally Posted by Folji

Decided to try and test this, see how it'd go.

Lua Code:

lib.CreateHealth = function(frame,frametype,width,height,point,x,y)
 
    local hp = CreateFrame('StatusBar',nil,frame)
    hp:SetSize(width,height)
    hp:SetPoint(point,frame,x,y)
    hp:SetStatusBarTexture('Interface\\AddOns\\TestUI\\media\\playerhp')
    hp:SetStatusBarColor(0,1,0)
    hp:RegisterUnitEvent('UNIT_HEALTH', frametype)
 
    if (frametype == 'target') then
        hp:SetReverseFill(true)
        hp:GetStatusBarTexture():SetTexCoord(1,0,0,1)
        hp:GetStatusBarTexture():SetPoint('RIGHT', hp)
    end
 
    local function HealthUpdate()
        local hpcur, hpmax = UnitHealth(frametype), UnitHealthMax(frametype)
        hp:SetMinMaxValues(0,hpmax)
        hp:SetValue(hpcur)
    end
 
    hp:HookScript("OnEvent",HealthUpdate)
 
    local function CheckCoords()
        print(frametype.." : "..hp:GetStatusBarTexture():GetPoint())
        print(hp:GetStatusBarTexture():GetTexCoord())
 
    end
 
    frame:HookScript('OnMouseUp',CheckCoords)
end

Seems like not being able to use hp:GetStatusBarTexture():SetTexCoord(1,0,0,1) to flip the texture is largely down to how the game handles statusbars? I don't know if I'm writing something wrong here or what, but testing around with it showed me that the statusbars were narrowing by changing the TexCoords directly. So no matter what it was set to before, it'd change back to 0,1,0,1 and then gradually drop down from there.

GetStatusBarTexture():GetPoint() defaulted to TOPLEFT, and trying to SetPoint() did absolutely nothing.

Hi Folji,

That's exactly what I have experienced.

Like you said, no matter what change is made, it changes back to 0, 1, 0, 1

Folji · 03-20-16, 07:00 PM

Yeah, seems it basically is just how the game does statusbars. The texture is anchored to the TOPLEFT of the statusbar, and the TexCoords are continually overwritten based on the percentage HP of the unit in question (at least that would be my assumption, as far as the percentage HP). Guess the texture anchoring might be hardcoded into the Blizzard function that updates statusbars?

zork · 03-21-16, 07:52 AM

Not a real issue though. Just create your own statusbar texture.

Layback_ · 03-21-16, 03:43 PM

Originally Posted by zork

Not a real issue though. Just create your own statusbar texture.

Like what you have done on your oUF_Doom? (That was awesome btw)

I actually have a question to ask regarding that.

When you create a doomHealth, don't you need to AddElement first (like oUF:AddElement('Health', Path, Enable, Disable))?

I don't really get how AddElement function works as there was no description written on API page

zork · 03-21-16, 04:38 PM

AddElement enables the element (module) you are looking at for the oUF framework. Basically the health element is like a module that needs to be enabled to work. You sort of register that module to oUF with that function call. Once you have done that you can use self.Health = myHealthStatusBar etc.

Layback_ · 03-21-16, 11:33 PM

Originally Posted by zork

AddElement enables the element (module) you are looking at for the oUF framework. Basically the health element is like a module that needs to be enabled to work. You sort of register that module to oUF with that function call. Once you have done that you can use self.Health = myHealthStatusBar etc.

What about the case of your oUF_Doom?

I had gone through your oUF_Doom and It does not seem to have oUF:AddElement("doomHealth", ...) something like this.

zork · 03-23-16, 04:07 AM

That is because oUF_Doom is using the default health element (module) that oUF is providing and which is available via self.Health = healthBar. I do not need my own element.

For example if you play a warlock and want to create your own soul shards module with oUF you can do it by creating your own element and registering it to oUF.

Layback_ · 03-25-16, 05:16 PM

Originally Posted by zork

That is because oUF_Doom is using the default health element (module) that oUF is providing and which is available via self.Health = healthBar. I do not need my own element.

For example if you play a warlock and want to create your own soul shards module with oUF you can do it by creating your own element and registering it to oUF.

Hi again zork,

But, doesn't that mean it has to be self.Health = doomHealth? not self.doomHealth = doomHealth?

I also used default health element, tried self.testHealth = Health and it didn't work since the default health element refers to self.Health as its health bar.