User talk:Eai: Difference between revisions
No edit summary |
(Re: Note) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
== Are player elements the only things that can't be wiped? == | == Are player elements the only things that can't be wiped? == | ||
Cause i'm pretty sure you can't touch the root node either. can you confirm this? | Cause i'm pretty sure you can't touch the root node either. can you confirm this? Can you also confirm that passing root as an arg to destroyElement will wipe out group structures, and place all players as child elements just off root? | ||
And just as a side question, if i destroy an object with child player elements, will the player elements be set as child elements of the parent of the element that was just destroyed? or will they be shuffled to root? | |||
== CloneElement Questions == | |||
1) Why is it documented as a fake function? | |||
2) I need verification that Players and the Root node elemebts cannot be cloned and that it will return false if attempted. | |||
3) Make sure that if an element has children that are player elements, those player elements are not cloned. | |||
4) What are the default values for the optional arguments used for this function. In particular, the cloneChildren argument. | |||
== Re: Note == | |||
The root element should NOT be clonable. by definition, its the root, and there should only be one of them. | |||
I cannot imagine any situation where you'd want to clone everything on the server at once anyway. |
Latest revision as of 15:14, 16 August 2006
Hey Eai, first request of the day.
I need a function header for createElement, and a good reason for its existence (I know about createvehicle, and its like, but this generic one mystifies me) Vandalite 21:43, 15 August 2006 (CDT)
Are player elements the only things that can't be wiped?
Cause i'm pretty sure you can't touch the root node either. can you confirm this? Can you also confirm that passing root as an arg to destroyElement will wipe out group structures, and place all players as child elements just off root?
And just as a side question, if i destroy an object with child player elements, will the player elements be set as child elements of the parent of the element that was just destroyed? or will they be shuffled to root?
CloneElement Questions
1) Why is it documented as a fake function?
2) I need verification that Players and the Root node elemebts cannot be cloned and that it will return false if attempted.
3) Make sure that if an element has children that are player elements, those player elements are not cloned.
4) What are the default values for the optional arguments used for this function. In particular, the cloneChildren argument.
Re: Note
The root element should NOT be clonable. by definition, its the root, and there should only be one of them.
I cannot imagine any situation where you'd want to clone everything on the server at once anyway.