texture:SetAtlas() and using cooldown swipe texture for rings.

[zork]

Interesting is this part:

if (rank > 1) then
        self.BuildingPulse:SetAtlas("Garr_BuildingUpgradeExplosion", true);
        self.AlphaPulse:SetAtlas("Garr_BuildingUpgradeExplosion", true);
        self.Timer.BG:SetAtlas("Garr_UpgradeIconTimerBG", true);
        self.Timer.CompleteRing:SetAtlas("Garr_UpgradeIconTimerFill", true);
        self.Timer.Cooldown:SetSwipeTexture("Interface\\Garrison\\Garr_TimerFill-Upgrade");
    else
        self.BuildingPulse:SetAtlas("Garr_BuildingPlacementExplosion", true);
        self.AlphaPulse:SetAtlas("Garr_BuildingPlacementExplosion", true);
        self.Timer.BG:SetAtlas("Garr_BuildingIconTimerBG", true);
        self.Timer.CompleteRing:SetAtlas("Garr_BuildingIconTimerFill", true);
        self.Timer.Cooldown:SetSwipeTexture("Interface\\Garrison\\Garr_TimerFill");
    end

https://github.com/tekkub/wow-ui-sou...ngUI.lua#L1626

So basically I had another idea for the ring stuff. Now that we have swipe textures we might just fake a ring by just implementing a cooldown frame with a ring swipe texture.

Additionally I found a lot of texture:SetAltlas(textureFile, true) calls. What is that?

http://wowprogramming.com/docs/widgets/Texture/SetAtlas

[Fizzlemizz]

Not overly informative but a start, from the 6.0.2 change list.

New "atlas" and "useAtlasSize" properties for textures defined in XML. Equivalent function added for texture widgets called Texture:SetAtlas. For example:

Before: file="Interface\PetBattles\PetJournal"
After: atlas="PetJournal-BattleSlot-Locked" useAtlasSize="true"

[semlar]

The only problem with using cooldown frames for this is that addons that hook the metatable to display time left (like omnicc) might end up drawing on your ring.

Atlases are basically hardcoded texture coordinates blizzard added so instead of having SetTexCoords all over the place they could use the name of the atlas, and if they need to update the coordinates for the texture they only need to do it in one place.

[Fizzlemizz]

Originally Posted by semlar Atlases are basically hardcoded texture coordinates blizzard added so instead of having SetTexCoords all over the place they could use the name of the atlas, and if they need to update the coordinates for the texture they only need to do it in one place.

Next question would be, do you know where/how they are defined? A search for Garr_UpgradeIconTimerBG only turned up the one SetAtlas() instance.

[semlar]

Originally Posted by Fizzlemizz Next question would be, do you know where/how they are defined? A search for Garr_UpgradeIconTimerBG only turned up the one SetAtlas() instance.

They're defined internally (not sure if there's a DBC file for it), and you can't create your own atlases, only reference the existing ones.

[Fizzlemizz]

Originally Posted by semlar They're defined internally (not sure if there's a DBC file for it), and you can't create your own atlases, only reference the existing ones.

Well, that puts paid to that idea .

Thank you.

[zork]

Yeah would be funny if OmniCC would add numbers to the rings. But there are attributes for that I guess.
Thanks for the info on the atlas.