[Xquartz-dev] 2.3.3_rc1

[Jeremy Huddleston]

On Mar 10, 2009, at 12:48, George Peter Staplin wrote:
>> I'm thinking we should just eliminate LIBGL_ALWAYS_HARDWARE and  
>> default
>> to that, but I'm going to let it sit for a few moments to see if  
>> George
>> knows of a good reason why we might want to avoid that.
>
> As I understand it, one argument against the kCGLPFANoRecovery I  
> think I recall reading about involves multiple shared displays.
>
> "kCGLPFANoRecovery
> This constant is a Boolean attribute. If it is present in the  
> attributes array, the OpenGL failure recovery mechanisms are  
> disabled. Normally, if an accelerated renderer fails due to lack of  
> resources, OpenGL automatically switches to another renderer. This  
> attribute disables these features so that rendering is always  
> performed by the chosen renderer. This attribute is not generally  
> useful. Do not supply a value with this constant because its  
> presence in the array implies true."

> If you try to drag a window using that pixel format between multiple  
> displays it might fail.

It worked here, but both of my displays are on the same physical  
card.  So I don't think it's between displays but possibly between  
displays that use different renderers.  Still, that is a good  
argumenta gainst that attribute.  I still think we should use  
kCGLPFAAccelerated by default.  But let's not make that switch until  
we've ironed out the details of Jack's issue (this way we have three  
codepaths to try: HW, SW, and "either").  In any case, it is  
worthwhile to find out what the app is requesting to find out why  
there is not a HW mode to support it.