Re: context type: UNDECIDED vs. CHROMIUM vs. NATIVE

I ran into some issues with these three types when I was trying to  
run Brook programs through Chromium on Windows for a paper push  
recently.  Unfortunately I was in such paper writing mode I don't  
remember what I did.  It had something to do with the fact that  
Chromium returns "Humper" as the GL_VENDOR if you do a glGetString()  
before any context is actually created (which is supposed to work).

I suspect that the pixel format bug is a serious one and was  
affecting our efforts to run FarCry through Chromium for that paper.

On May 25, 2005, at 5:19 PM, [email protected] wrote:

> Hi all,
>
> Could someone clarify the intent of the three different Context types:
> UNDECIDED, CHROMIUM, and NATIVE.
>
> I'm running into a situation where contexts (i.e. windows) aren't  
> being
> deleted, because their type is UNDECIDED.
>
> The function stubDeleteContext in opengl_stub/context.c only takes  
> action if
> the type is NATIVE or CHROMIUM, so contexts that are created under  
> windows
> (wgl.c:wglCreateContext_prox) never get deleted.
>
>
> The result is that apps which create contexts just for the sake of  
> querying
> capabilities end up spawning tens or hundreds of windows.
>
>
> Thanks as always,
> Jon Marbach
>
> Univesity of Colorado at Boulder
> BP Center for Visualization
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way to  
> collaborate
> online with coworkers and clients while avoiding the high cost of  
> travel and
> communications. There is no equipment to buy and you can meet as  
> often as
> you want. Try it free.http://ads.osdn.com/? 
> ad_id=7402&alloc_id=16135&op=click
> _______________________________________________
> Chromium-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chromium-dev
>
>

--
Greg Humphreys, Assistant Professor
Department of Computer Science, University of Virginia
http://www.cs.virginia.edu/~humper/