Hi Robert, I'll do these modifications and check them tonight when I'm back home. To speed things up (and because we're going to backport OSG changes), I'm not going to do a full release on TriStripper website yet; instead I'll send you a zip containing the updated version.
Cheers, Tanguy -----Original Message----- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield Sent: 24 November 2009 3:33 PM To: OpenSceneGraph Users Subject: Re: [osg-users] TriStripVisitor issue Hi Tanguy, On Tue, Nov 24, 2009 at 2:55 PM, Tanguy Fautre <tang...@aristechnologies.com> wrote: > http://users.telenet.be/tfautre/softdev/tristripper/ Thanks the link and explanation. > After a quick look at the header, I've noticed protections against > min/max macros that will cause a hard failure when those are detected > (which you probably want to avoid in a library such as OSG). Thinking > about it now, this is a bit harsh as I've learned since now how to avoid > macro expansion. For example, replacing > > const size_t Overlap = std::min(PossibleOverlap, size()); > > by > > const size_t Overlap = (std::min)(PossibleOverlap, size()); > > will avoid the macro replacement and use the std function instead. Is there any chance you can max this fix the TriStripper before I take a copy and merge it with the OSG? Cheers, Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or g _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
