What has a Shape3D to do with passing the coordinates by reference or by copy to a Geometry object ? Second, if you use geometry by reference, you can update it EVEN if the branch group is compiled and live - see GeometryUpdater.
For your case, as I see it and you have explained, you can simply create ONE Geometry object, either passing the coordinates / normals by reference or by copy, it doesn't matter, and use that single Geometry object to create as many Shape3D as you like. You don't have to create for every Shape3D a different Geometry object with the same coordinates. Cheers, Florin -----Ursprüngliche Nachricht----- Von: Ian M Nieves [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 6. Januar 2003 12:02 An: [EMAIL PROTECTED] Betreff: Re: [JAVA3D] AW: [JAVA3D] size of transform3D and transformGroup Florin, It was my understanding that geometry by reference simply allows one to hand geometry to a shape3d, without requiring the shape3d to make its own internal copy. Therefore, it eliminates the need for a copy operation. I dont believe that any indirection is added. A reference to geometry is always needed somewhere, regardless of if that geometry is a copy or an original. Therefore, I dont believe that by reference, performance is negatively impacted. Further, I dont believe this has anything to do with updating geometry. Geometry can always be updated, unless the branch group is compiled. Thoughts? Ian On Mon, 6 Jan 2003, Florin Herinean wrote: > Using geometry by reference only makes sense when you want to modify the > geometry at runtime, otherwise you just introduce another level of > indirection and hinder possible optimizations. > > Cheers, > > Florin > > -----Ursprüngliche Nachricht----- > Von: Ian M Nieves [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 6. Januar 2003 09:55 > An: [EMAIL PROTECTED] > Betreff: Re: [JAVA3D] size of transform3D and transformGroup > > > Hans, > > Thanks for your reply. Your point is very clearly made. > > I may be in trouble though. I might want to be able to share geometry, > but have different appearances. I will have to look into this more. > > Another question though. Is is possible for me to use geometry and > normals, by reference (instead of by copy), and have each reference point > to a single, shared static version of the geometry and normals? Would > that have any effect? > > Thanks,Ian ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
