Has anyone tested using standard window objects in a window that also had an opengl/d3d context?
I believe Terragen 2 is attempting to do this. If this hasn't been tested, than it might be the cause of all of the static that appears non opengl area, making the program nearly unusable.
No messages get printed to the console from wine(Terragen 2 prints out a fair bit of debug info there, but nothing from wine that would cause the problem, just a few warnings that shouldn't be related).
Any thoughts?
Am Freitag 09 März 2007 19:47 schrieb Mike Schaadt:
Has anyone tested using standard window objects in a window that also had an opengl/d3d context?
This is known not to work. It was a regression due to the window management rewrite.
The problem is that since the window management rewrite all window elements except the main window are not X11 windows. So the clipping done by X11 on opengl contexts does not work for subwindows in wine.
The current plan for fixing this is, I believe, to create an overlay window which is used for opengl drawing. The other idea was to set up the opengl scissor test, but that turned out not to work correctly, and we need a seperate window for antialiasing support too.
Ah so that was the infamous problem with things like the WC3 Map editor, and such? Thinking about that not it makes sense.
On 3/9/07, Stefan Dösinger stefandoesinger@gmx.at wrote:
Am Freitag 09 März 2007 19:47 schrieb Mike Schaadt:
Has anyone tested using standard window objects in a window that also
had
an opengl/d3d context?
This is known not to work. It was a regression due to the window management rewrite.
The problem is that since the window management rewrite all window elements except the main window are not X11 windows. So the clipping done by X11 on opengl contexts does not work for subwindows in wine.
The current plan for fixing this is, I believe, to create an overlay window which is used for opengl drawing. The other idea was to set up the opengl scissor test, but that turned out not to work correctly, and we need a seperate window for antialiasing support too.
On 10/03/07, Bryan Haskins kingofallhearts999@gmail.com wrote:
Ah so that was the infamous problem with things like the WC3 Map editor, and such? Thinking about that not it makes sense.
See http://bugs.winehq.org/show_bug.cgi?id=2398 and http://www.winehq.org/pipermail/wine-devel/2006-December/053084.html
Ah, alright, and I meant now instead of not. Me and my typos... always are inconvenient. Anyway, thanks for the info!
On 3/9/07, H. Verbeet hverbeet@gmail.com wrote:
On 10/03/07, Bryan Haskins kingofallhearts999@gmail.com wrote:
Ah so that was the infamous problem with things like the WC3 Map editor,
and
such? Thinking about that not it makes sense.
See http://bugs.winehq.org/show_bug.cgi?id=2398 and http://www.winehq.org/pipermail/wine-devel/2006-December/053084.html