Problems with Hide() and templates in xml

[zmga]

I'm having an interesting issue with the :Hide() function on my textures. While I am able to show them using texture:Show(), the same texture will return the following error when using texture:Hide()

attempt to call method 'Hide" (a table value)

This problem appears whenever I define my textures in xml with a template


My xml currently follows this kind of logic:

<Texture name="TextureTemplate" virtual="true"> <size, anchors, animations, etc> </size, anchors, animations, etc> </Texture> <Frame name="Myframe"> <Size, Anchors, etc> </Size, Anchors, etc> <Layers> <Layer level="ARTWORK"> <Texture name ="$parent1" file="Interface\AddOns…1" inherits="TextureTemplate"/> <Texture name ="$parent2" file="Interface\AddOns…2" inherits="TextureTemplate"/> </Layer> </Layers> </Frame>

I assume that defining the texture file in this way is causing the problem but why am I able to show() but not hide()?

How else should I organize my xml so I wouldn't have to repeatedly apply the same animation groups to different texture files?

[Duugu]

I've actually never seen someone using templates for textures. Are you sure that this is supported? Or is this just a shot in the dark to see if it's supported?

You could create the textures via lua.

[e]
btw, what does print(type(<yourtextureobject>.Hide)) report?
And /dump <yourtextureobject>.Hide?

[zmga]

I would assume that it is supported. Blizzard uses texture templates here and there, but not really often enough that I got a clear sense of how it should work.

I based my code on the GlueTemplates.xml and QuestChoice.xml


In the files above they use the template to define the file and assign anchors in the actual texture. I want to do the opposite but this shouldn't make a difference if the template works at all, right?

Maybe there is a gotcha with transferring over names and you need to use relative key.




EDIT: Problem Solved!

It turns out one of my animations had the parentkey Hide. Thanks to Duugu for the help.

Btw does anybody know why this is even a problem? Why does the parent key on an animation override the Hide() command?

[Fizzlemizz]

My guess would be the "parent" part of parentkey.

[Phanx]

XML is painfully verbose and ugly, but....

<Frame name="MyFrame">
     <Frames>
          <Frame parentKey="Hide">
                <!-- some stuff here -->
          </Frame>
     </Frames>
</Frame>

... is the same as doing this:

CreateFrame("Frame", nil, "MyFrame")
MyFrame.Hide = CreateFrame("Frame")

Hopefully you can see how that would cause problems when attempting to call MyFrame:Hide() !

[zmga]

CreateFrame("Frame", nil, "MyFrame")
MyFrame.Hide = CreateFrame("Frame")

Hopefully you can see how that would cause problems when attempting to call MyFrame:Hide() ![/quote]

Sorry, I'm not very versed in lua (or xml for that matter) so more explanation would be helpful. I just assumed that x:hide() was different from x.hide.

Looking it up in the lua wiki it seems that x:hide() is the same thing as x.hide(x) but I'm not quite why that is…

[SDPhantom]

The colon syntax is used for defining methods, that is, functions that have an implicit extra parameter self. Thus, the statement function t.a.b.c:f (params) body end is syntactic sugar for t.a.b.c.f = function (self, params) body end

Lua 5.1 Reference Manual §2.5.9

[Gethe]

Originally Posted by zmga CreateFrame("Frame", nil, "MyFrame") MyFrame.Hide = CreateFrame("Frame") Hopefully you can see how that would cause problems when attempting to call MyFrame:Hide() ! Sorry, I'm not very versed in lua (or xml for that matter) so more explanation would be helpful. I just assumed that x:hide() was different from x.hide. Looking it up in the lua wiki it seems that x:hide() is the same thing as x.hide(x) but I'm not quite why that is…

There was some good discussion about this last week in this thread.