Hello Carsten, as far as I can see the problems we had are gone now. So thank you very much for fixing. From our side you may go ahead and commit the made changes...
Thanks, Michael p.s. any news from mcast section? -------- Original-Nachricht -------- > Datum: Wed, 16 Nov 2011 11:42:41 -0600 > Von: Carsten Neumann <[email protected]> > An: [email protected] > Betreff: Re: [Opensg-users] OpenSG1.8 - Geometry functions > Hello Michael, > > On 11/15/2011 01:07 PM, Michael Raab wrote: > > 3. calling calcVertexNormals(geo, angle) first, then > > calcVertexNormal(geo), then calcVertexNormals(geo, angle) again > > and so on also increases the indices size > > calcVertexNormals(geo, angle) now looks for an index that does not have > a mapping (getIndexMapping(i) == 0) and reuses that instead of always > adding a new index. Patch attached. > The calcVertexNormals(geo) version could be changed to remove these > unused indices, but it otherwise tries to go out of its way to minimize > changes to (shared) properties [1], so that did not seem like a good fit. > > Cheers, > Carsten > > [1] I don't know why it was written that way and why other functions do > not pay attention to shared properties. IMHO the geo functions are > complicated enough, they could perhaps warn if they encounter shared > properties, but should otherwise assume the caller knows what they are > doing. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
