This will work in the current implementation, but it is technically one of those "undefined behavior" cases.
Doug Twilleager Java 3D Team Sun Microsystems >Subject: Re: [JAVA3D] Geometry Update >To: [EMAIL PROTECTED] >MIME-version: 1.0 >Delivered-to: [EMAIL PROTECTED] > >Ooh this is a good one! > >Since it is considered illegal to update the vertices of by-ref geometry >outside of a geometry updater it would be "bad" to do as you have suggested. >However, I am not sure if it would actually be a problem if you do this from >a behavior since I would expect that both geometry array's would already be >winging their way to the card. But if you wanted to play it safe, try >making a dummy updator that does nothing but invoke the other updater on the >other geometry array. This should lock both at the same time. You could >even build a generic class that could manage "shared by-ref geometry" to >provide this locking. > >Dave Yazel > >-----Original Message----- > >From: Michael Nischt [mailto:[EMAIL PROTECTED]] >Sent: Monday, April 01, 2002 1:16 PM >To: [EMAIL PROTECTED] >Subject: [JAVA3D] Geometry Update > > >hello everyone, > >I have an question concerning geometry-update, with shared vertices: > >Two (Indexed)GeometryArrays (BY_REFERENCE) share the same vertices (with >different indices), because some parts have different Materials. >I decided to put the same cordinate/normal arrays in both and I update one >with a GeometryUpdater, and both were updated correct. :-) > >But I am wondering if this legal, because the second one has no >GeometryUpdater ? do I have to put an dummy updater for the second one ? > >greetings >-Michael Nischt > >btw. a Test application is attached for better understanding > > > =========================================================================== 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".
