Child was added as a result of a convo I had with the folks at SOE. Basicly there may be cases where you need to address a child object who's name happens to match a property tag (Name="Name", Name="Text", Name="Size", etc). Durring the convo we thought there might be issues pathing to the child object rather then getting the parent object's atribute. Foo.Text could be a reference to the text property of Foo or to a child object of Foo named Text.
After the child operator was added to test, we realized (as Death mentioned) there are few cases where this would cause a prob since the script parser knows a trailing dot indicates child pathing.
The only time you'd need this is when addressing the object directly and not its properties or child nodes. Show_window(Foo.child.Text) Hide_window(Foo.child.Text).
Other more advanced applications that might be possible (depending how fully this was implemented) include copying an entire object and its properties. Foo.PageB = Foo.child.Page. I'm guessing this last example isn't possible but haven't confirmed.
|