Why is there not a Node.detach() function? In order to detach a Node
child from its parent, currently you have to go to the parent, then
search the list of its children to find the index of the one you want to
detach, then call Group.removeChild(index). (Am I missing some better
way of doing
]
-Original Message-
From: Rob Nugent [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 01, 2000 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
J. Lee,
I made this mistake (and asked this question a few months back).
There is a detach() method in BranchGroup
[home]
Memorial University of Newfoundland (709) 749-4383 [cell]
-Original Message-
From: Rob Nugent [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 01, 2000 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
J. Lee,
I made this mistake (and asked
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
Rob and everyone else,
On a related note then... why is there only BranchGroup.detach() and not a
general Node.detach()? It makes scenes much larger when you have many
shapes, each with it's own BranchGroup to allow the shapes
[home]
Memorial University of Newfoundland (709) 749-4383 [cell]
-Original Message-
From: Pondrom, Pierre L [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 01, 2000 11:15 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
I would like to give my users the capability
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
Chris and the list,
Probably by keeping detach() in only BranchGroup it is easier to
do
the optimizations when a scenegraph is compiled. That would be my
guess.
-Original Message-
From: Christopher Collins [mailto
--
From: Christopher
Collins[SMTP:[EMAIL PROTECTED]]
Reply To: Discussion list for Java 3D API
Sent: Tuesday, August 01, 2000 9:26 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] detach() suggestion
Hi Pierre,
This is simplistic, but couldn't you have each
: [JAVA3D] detach() suggestion
How about this, in addition to the existing Group.removeChild(index), we
have Group.removeChild(Node). Then, the Group parent could search its
list, find the node, and call .removeChild(index) on its own. Then, one
step further, Node.removeFromParent() would just call
