http://bugs.winehq.org/show_bug.cgi?id=11826
--- Comment #18 from Zak Mayer zak.mayer@gmail.com 2008-03-17 15:56:48 --- Additionally I've seen this old post: http://www.winehq.org/pipermail/wine-patches/2006-December/033938.html
Although I'm not certain of its relevancy to this situation. I don't see how pbuffer support would be pulled from a driver only to re-implement it down the road, but one never can tell.
Additionally in gdi32 the call for the stub in the gdi32 spec is commented out: # @ stub GdiSwapBuffers Obviously I have no clue what this means for the overall pbuffer support but I've been able to see that it and several other buffer objects(methods,variables) are working with pbuffer support in Wine. OpenGl.spec calls - @ stdcall wglSwapBuffers(long) gdi32.SwapBuffers Which is @ stdcall SwapBuffers(long) in the gdi32.spec
I haven't been able to review the code beyond this and if it isn't obvious already I am quit lost as to what is getting called when and where. However given past reading and examples that I've found throughout the Wine project it looks as if pbuffer is and has been and continues to be a pita.