<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Space Rangers 2 (in Wine) shows only black screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=91171#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Space Rangers 2 (in Wine) shows only black screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=91171">bug 91171</a> from <a class="email" href="mailto:hverbeet@gmail.com" title="Henri Verbeet <hverbeet@gmail.com>"> Henri Verbeet</a> <pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=91171#c4">comment #4</a>) > discarding the old stuff. [Looks like it does both glXCreateContext *and* > glXCreateContextAttribsARB, and discards the first one of those.] > Yeah... we first need a context to be able to call wglGetProcAddress(), to get the wglCreateContextAttribsARB() pointer. > I was looking over what flush did, and it does indeed explicitly flush the > frontbuffer to screen if it's the current drawbuffer. [or something along > those lines]. Tracing through that flow, it's entirely over my head... > interactions between multiple modules of which I know nothing. I don't see > anywhere where it'd be waiting for that blit to complete either, but that > doesn't mean it's not there. Perhaps this should be a glFinish()? > We don't wait for it to finish, but we shouldn't have to.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>