Originally Posted by merlight
You create a <Control> with attribute inherits="ZO_ScrollList". ZO_ScrollList is itself a <Control> with attribute virtual="true".
In Garkin's XML above, it's this part (with ZO_ScrollContainer instead):
ZO_ScrollContainer is a control that contains the slider bar, buttons and the scrolled area, which is named "$(parent)ScrollChild".
"EventExplorerWindow" -> "Container" -> "ScrollChild" is then named EventExplorerWindowContainerScrollChild in _G, look that up in Garkins code, this control is used as the parent of created rows.
|
So instead of being a seperate type of control (like <Label/>, <EditBox/> and the like) that has other elements as childs, the scroll container is a "Control" whose inherits atribute was set? The same way you set a <Backdrop/> inherits atrbute, to tell it wich Backdrop it has to look like?
I try to get some understanding of what happens via the rules that apply to WPF. There writing code like this:
xml Code:
<Label>
<Content>
"Test"
<Content/>
</Label>
would just be different syntax for this:
With the first syntax having the potentioal for a lot more complex content then a mere string (A label could contain a image. Or a container that in turn has dozens of sub elments).
Going from there:
xml Code:
<GuiXml>
<Controls>
</Controls>
</GuiXML>
I just the way to set the "Controls" Field/Property of the GuiXML element.
Wich elements all have a "Controls" property and are thus containers?
Is it only "GuiXML", "Control" and "TopLevelControl"? All of them? All of them but a few?