Hi, We're using VisitSubTree to reduce the amount of nodes needed, as we have one largish component (~200 nodes) in two places, and looking at the debug output (my graph generator in the utils dir on the wiki) is a bit horrible with many nodes.
So, VisitSubTree works fine, but IntersectAction probably needs some work in order to show the correct path. (Yes, I know, I'm going down a multiple-parents-per-node path here, which OpenSG tries to avoid) Nevertheless, what I mostly need is the actual to-world transform of the intersected node, not necessarily the entire path from root to node. (Although it might be handy to have as well...) Does it seem a reasonable thing to fix? If so, how should I go about patching that? Either just grab the transform and add get-function for it (similar to Point/Object/Normal) or is there some better way? Cheers /Marcus ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
