From: <ma...@co...> - 2005-05-26 16:01:29
|
Brian, Let me first say that I think Chromium is great! And I'm so glad it supports Win32 at all! So thank you everyone who's got Chromium on Win32 this far. I'm happy to be working on expanding the robustness of Chromium on Win32. > What capabilities would be queried, and how (without making current)? If I only knew! (I think these apps assume that the last created context is automatically made current.) Literally, one of the apps names its WindowClass "query". (WindowClass is a Win32 thing - it's an internal window name.) Another app is naming the window classes "OpenGL Info Window". It seems pretty clear that these apps are creating hidden windows, and creating contexts for them, in the hopes of discovering some properties of the OpenGL driver. While it may not be the "right" way to do it, they do it! And I don't think I have enough pull to convince them to change their source code. The lovely part of all this is you have to guess what the 3rd party app is doing - it's like detective work... It seems as though the apps I'm testing create a context, then do a GetPixelFormat to see if the context was created according to spec, i.e., with the PixelFormat that was requested... In short, some apps are very picky about what pixelFormats are available, and I'm working on expanding the WGL implementation to make those picky apps happy. > I'm still not 100% clear on whether the issue is with rendering > contexts or with windows. You mentioned that the window stays up. > Are there many rendering contexts and one window, or many rendering > contexts and many windows? I may be speaking too soon here, but it looks like Chromium, at least in "stand alone" mode, creates a new render spu (and a new window for the spu) every time stubCreateContext is called. But before I blah blah blah about all this any further, I'll be investigating this further this afternoon, so I'll get back to you on it with clearer info. Thanks for the help and advice! Jon |