Hi David,

I have started work on refactoring osg::Geometry (view the new
osg::GeometryNew class) and as one of the steps am moving the
normalize flag into osg::Array as a s/getNormalize() and while I'm at
in I'm adding a the API for the integer/double setVertexAttrib*()
functions:

        /** Set hint to ask that the array data is passed via integer
or double, or normal setVertexAttribPointer function.*/
        void setPreserveDataType(bool preserve) { _preserveDataType =
preserve; }

        /** Get hint to ask that the array data is passed via integer
or double, or normal setVertexAttribPointer function.*/
        bool getPreserveDataType() const { return _preserveDataType; }

Does this feel appropriate naming?

I won't implement any of the backend for it at this current point but
leave this to after the rest of GeometryNew has started to settle.
The general refactor work will impact osg::State and the
ArrayDispatchers and should simplify them a bit, my hope that this
will open a door to efficiently support the integer and double
attribute arrays - this is just arm waving right now.

Once I've got further with the refactor it'll worth you having a look
to see any opportunities to implement the original functionality you
were after in the new scheme.

Cheers,
Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to