WoWInterface - i have yet another question ( best title i could think of )

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

- General Authoring Discussion (https://www.wowinterface.com/forums/forumdisplay.php?f=20)

- - i have yet another question ( best title i could think of ) (https://www.wowinterface.com/forums/showthread.php?t=32087)

i have yet another question ( best title i could think of )

alUI.texture = "Interface\\AddOns\\texture"
--[[ lets say this is going on up here ]]--

very @n4l question here. (hope i'm allowed to say @n4l). gently caress it.

So I've been looking through the code of many minimal UIs (rec, cael, nc, clean, etcc). I'm just wondering what effect on CPU performance does or even memory

Code:

example:SetTexture(alUI.Texture)

in comparison to

Code:

example:SetTexture("Interface\\AddOns\\texture")

Imagine this @ a larger scale ofc. taking in fonts, various integer sizes etc.

hopefully you understand what I mean. But yeah, I'm just wondering, is it simply convenience or are there reasons beyond my noob understanding?

Quote:

Originally Posted by alimjocox (Post 185835)

Code:

example:SetTexture(alUI.Texture)

in comparison to

Code:

example:SetTexture("Interface\\AddOns\\texture")

Does it matter? alUI.Texture is much much more easy to maintain, because you can change all the textures in one shot in one location, instead of having to find and replace every single "Interface\\AddOns\\texture".

To answer the question, it MIGHT differ a few bytes, so if you that that 1000 times you've saved a kilobyte! YAAAAY!!!!! (srsly, doesn't matter)

Quote:

Originally Posted by nightcracker (Post 185837)

cool thx. I was under the impression since its a global thing it might make the CPU work a nano of a fraction harder (I DONT KNOW lol). especially if the 'sed' texture is declared often.

If that is totally wrong - glad to be learning ;)