From: Mick P. <mic...@wi...> - 2017-06-18 04:39:27
|
I'm not having fun on Cygwin. I'm running Nigel's GLUI example projects. Cygwin's freeglut package is the GLUT implementation. glutHideWindow produces the following output: wglMakeCurrent error: 00000006 wglMakeCurrent error: 00000006 wglMakeCurrent error: 00000006 These continue after the window is reclaimed by glutShowWindow. At this point it cannot redraw itself. If anyone cases its the 6th example I'm mainly looking at. I'm running it on Cygwin to add try to facilitate copy/paste with X. Cygwin is most convenient. I tried -indirect mode but got the following output. X Error of failed request: GLXBadContext Major opcode of failed request: 150 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 56 Current serial number in output stream: 55 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 150 (GLX) Minor opcode of failed request: 24 (X_GLXCreateNewContext) Value in failed request: 0x0 Serial number of failed request: 55 Current serial number in output stream: 56 This may be normal, but I'm not positioned to rebuild the freeglut or X packages, and tried to see if the results are different. There are freeglut-2.8.1-1 sources under /usr/src/debug, but they don't appear up-to-date at all. Anyway, it seems that hiding the window invalidates the WGL context. The README.cygwin_mingw file suggests that CMake will not generate Cygwin makefiles to freeglut's liking. I don't think that the example code is wrong. If I build a new freeglut, it won't help the Cygwin package situation. Minimizing the windows is fine. XUnmapWindow followed by XFlush starts the WGL errors. Early tests painted junk in the device context over the unhidden window. But I changed something so it tries to draw itself, but this just results in a black non-client area. -- As with mail, anyone who wishes may send email from your email address. In the case you receive obscene or unusual email from an address with which you are familiar. It could be someone is impersonating that email address. Always return a copy of the email to the sender for review and response. |