Hi Robert,
Currently, if a GraphicsWindowWin32 is created with traits->useCursor =
false, it still shows the cursor. An app must call gw->useCursor(false)
after having created the context as a workaround, but I think what we ask
for in the traits should be honored... Attached is a simple fix for this.
Thanks JS, change now merged and submitted to svn/trunk.
Thanks, I did mention that this seemed to be a regression right? Perhaps
it could be noted as such in the (future release) release notes.
There is the issue of order of execution that you'd have to be careful
about when setting up any subclass state so in general I'd suggest
it's safer to late the subclasses do the right thing by their own
needs.
You mean order of execution of base-class / derived-class constructors?
There could be a protected init() method that subclasses could call or
not, and where common initialization could be done. But it doesn't
really matter, we can just fix issues as they arise too.
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
