Hi Robert,
> I don't think it should be a case of shrugging ones shoulders and
> excepting that Windows doesn't work properly and documenting this.
> osgViewer should behave the same on all platforms as far as we can
> possibly make it.
I'm not saying Windows does not work properly, just it does things
differently. Policies and driver implementations are different, nothing
we can do about it.
Though we can hide it, and I agree osgViewer should do the same thing
(visually) on all platforms.
> If full screen under windows trips windows up so that it grabs all
> screens then its something we can only use when osgViewer is running
> over all screens, when this isn't the case a borderless full screen
> window will probably have to be used.
Before we go and put in a workaround in osgViewer itself for this, let
me have a look at some documentation and see how GraphicsWindowWin32 is
implemented. Maybe there's something there that can give some clues.
It seems that the flag "windowDecorations" in the traits structure is
what's triggering this. Even if I want to do my borderless window
workaround, I need to pass the traits with windowDecorations=true when
creating the window, and then disable them
(gw->setWindowDecorations(false)) afterwards, otherwise still I get the
black screen on the other screen.
Also, the fact no one else on Windows has come forward to comment on
this makes me doubtful. I'm not that familiar with implementing
windowing on Windows, so it may be some detail I'm not familiar with.
I'll get back to you.
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
