Originally Posted by Rostok
You should use 1.5.2
And there's not much code changed with the Factory you should take a look at some other layout, it's really not difficult to have your layout using it.
For the frame name, i give a name too and all my frames (i think so, didn't test raid) work like it should. So this has nothing to do with it.
You should have a pastey ready when you have a problem, it's so much easier when you have the code to help debugging it ^^
|
oUF generates name for you based on the style and unit if you don't specify one.
Originally Posted by ForeverTheGM
Regarding portraits:
Are there any workarounds for this? I don't want to disable portraits for my party and I need the visibility conditions, so that it displays when in a 5-man raid.
What am I to do?
|
Wait for Blizzard to fix it. =/
Originally Posted by Sueisfine
Hello there.
First of all thank you haste for all the hard work on 1.5.x /bow
I'm also in the process of migrating my personal layout to 1.5.x and so far I managed to fix most of the stuff but I'm running into a couple of issues and am wondering if someone can point me in the right direction:
1) Right-Click a player buff to cancel it: it isn't working atm, it throws an error popup in the game. any ideas of what I can do to fix this?
2) Concerning 'oUF-initialConfigFunction': I understand what you have to do if you want to use local variables inside the string (haste's example on first page). But is it also possible to call a local function inside the string? I mean, some function defined before the "SpawnHeader" call? If so, how can we do it?
Thank you very much in advance !!!
@neverg: I ran into the same issue you mentioned (frames not visible) and in my case the problem was the "initial-*' attributes that I was using to define the frames' size. I simply replaced those by ":GetWidth()" and ":GetHeight()" calls and it solved it for me. <pt>ja agora, sou portugues tb por isso se quiseres podemos depois discutir algumas cenas de codigo por pm ou assim </pt>
@people having issues with 1-pixel borders showing fuzzy after 4.0.1: according to http://www.wowinterface.com/forums/s...t=31813&page=4 it seems they changed the way the game's "uiscale" feature works. It seems now you have to disable it (i.e., uncheck the box in the in-game settings) in order to have the same effect as setting "uiscale" to "768/<your resolution height>" prior to 4.0.1. Just a heads up for those interested!
|
1) Use the SecureAuraHeader to do it, it's not an easy-piece of code to work with tho'.
2) No, you'll have to define it in that string. (or as a string in an attribute, which you can run through self:GetParent():Run('attributeName'), but that will have restrictions you won't like).
Originally Posted by Goldpaw
Couldn't find anything about it here, so I'll mention it:
The cooldown spirals on auras on the party frames flicker as well. Only the cooldown spirals though, not the auras themselves.
I'm guessing this bug is related to the RegisterAttributeDrive bug that causes portraits to flicker?
|
Yes it's related to RegisterAttributeDriver.