Hi Paul,
On 6/27/07, Paul Martz <[EMAIL PROTECTED]> wrote:
> The defaults in these cases are to do something sensible by default.
> No lighting and no depth test by default would lead to a
> pretty poor out of the box experience for most users needs.
Seems to have worked out OK for OpenGL over the past 14 years or so. :-)
But... OSG users expect a little more for free :-)
Anyhow, a quick review of this thread shows that I didn't propose changing
OSG's default, so I'm not sure how we got off on this tangent. I was just
speculating as to why so many users are confused about how to disable or
override lighting state. It probably has nothing to do with the fact that
core OSG changes the OpenGL default behavior. But it certainly does seem to
be a consistent stumbling block, and I'm not sure what the explanation is
for this confusion.
Is suspect its an issue with the relationship between OpenGL
attributes and modes, and naming. For instance
viewer.setLightingMode(NO_LIGHT); actually means that the view does
assign any setting for glLight, wheras this method could be thought of
as NO_LIGHTING which it isn't - lighting is still enabled, so there is
still light. Even the english language here can be a bit misleading
too.
Do you have any ideas on this, Robert?
Perhaps more explictly naming of enums i.e. more words to explain
exactly what it means. In the setLightingMode case I used the old
SceneView convention in osg::View in the hope it would buy more
familiarity with end users. But if the original SceneView one was
open to mis-interpretation then....
Better documentation too... now there's a thought, over to you :-)
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
