Thanks for the info.
I don't expect it to be integrated. I don't have a good understanding of 
either, but it seems the shadow window needs to be dealt with properly 
somehow.
This is a good start for the Core 3.2 support though.

Cheers,
Adam

On Tuesday, September 18, 2012 6:32:53 AM UTC+10, T.J. Jankun-Kelly wrote:
>
> AFAIK, the patch was never officially integrated (though there looks to be 
> activity now). I hacked together something that worked for me at the time a 
> year ago so I could teach my class; I cannot profess a deep understanding 
> of the OS or pyglet internals (thus the note that someone more experienced 
> in either could fix the issues I could not).
>
> TJK
>
> On Sunday, September 16, 2012 12:20:22 PM UTC-5, Adam Griffiths wrote:
>>
>> Any further progress on this?
>> I integrated your patch into my Pyglet tree and I get a segfault when 
>> running the 3.2 test harness.
>> I'm using Mountain Lion.
>>
>> I did notice a few changes to the cocoa.py file since your patch, but 
>> they look harmless.
>>
>> Cheers,
>> Adam
>>
>> On Monday, September 12, 2011 7:32:16 AM UTC+10, T.J. Jankun-Kelly wrote:
>>>
>>> I banged on this during the weekend and have it mostly working with 
>>> one issue: I have to disable the shadow window to get it to work. The 
>>> shadow window creates a default context (with a Legacy Profile); when 
>>> a Core Profile is created afterwards, OS X complains that it is an 
>>> invalid share as they are different profiles (http:// 
>>> developer.apple.com/library/mac/#documentation/GraphicsImaging/ 
>>> Conceptual/OpenGL-MacProgGuide/opengl_contexts/opengl_contexts.html#// 
>>> apple_ref/doc/uid/TP40001987-CH216-SW12<http://developer.apple.com/library/mac/#documentation/GraphicsImaging/Conceptual/OpenGL-MacProgGuide/opengl_contexts/opengl_contexts.html%23//apple_ref/doc/uid/TP40001987-CH216-SW12>).
>>>  
>>> To fix this globally would 
>>> require  doing something like adding a "shadow profile" option that 
>>> would be used by the shadow window. 
>>>
>>> I created an issue here to follow this patch: 
>>>
>>> http://code.google.com/p/pyglet/issues/detail?id=532&colspec=ID%20Status%20Type%20Milestone%20OpSys%20Summary
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/pyglet-users/-/1SvMdMfRQA4J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en.

Reply via email to