Hi Brad, On Thu, Oct 14, 2010 at 12:41 PM, Christiansen, Brad <[email protected]> wrote: > Every time I touch windows programming I cringe and generaly run as fast as I > can in the other direction. Unfortunately this isnt always possible. > I have a feeling some of the other glu functions may suffer the same windows > missery. Do any of the other examples use the new functions that you know of? > If so I will do some testing and try and ensure they work on windows as well.
There are essentially three parts of GLU that I've pulled in. The parts are: 1) Error message string gluErrorString(), this is very simple 2) Mipmapping and gluScaleImage functions, all in glu/libutil/mipmap.cpp 3) Tessellation all found in glu/libtess Part 1 is used is various of places over the OSG when checking OpenGL errors. Run the OSG and get an OpenGL error message and you'll be exercising this part. Part 2 if the OSG generates mipmaps on the CPU or rescales imagery then it'll be stressing this part. The running osggeometry example will invoke a rescale of the non power of two image, so is a place to see a quick test of the new functionality. Part 3 is stressed by osgtext3D and osgtessellate. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
