Thanks for your answers Dirk and Marcus. > You could do that. It would be more efficient to either add a > new Action > for it or to generalize the existing IntersectAction. The > main thing to > do would be to remove the optimizations that speed up the > intersection > process. ;) I think either one would work, changing the > existing one is > probably easier. I would add a callback function to be called > whenever a > hit is detected, to allow you to do what you want with the data.
OK. Thanks. > > - I would like to get the SG traversal path from the picked node(s) > > back to the root node. How can this be done? I was wondering if I > > would run into issues with respect to multiple parents for a given > > node? E.g. the 4 wheels of the car (in Dirk's slides), which is > > represented by the same node with 4 transform nodes as parents. > > As Marcus said this is not an issue with OpenSG, as the Intersect > returns the Node, not the Core. A related question. If I had to replicate existing subgraphs in my SG, say by inserting a xform node and then copy-pasting the subgraph as a child to a new transform node, what would be the most efficient way to do this? Since I can't use the root node of the subgraph again, what would be the best way to do this "cloning"? The brute force scheme would be to traverse the complete subgraph, create corresponding new nodes and assign them the cores from the original nodes in the subgraph. Has anyone done something like this before? What is the performance overhead? - Praveen ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
