On 14. May 2010, at 16:21, Stephen Furlani wrote: > I added `getWindow()->makeCurrent(false)` and stepping through that > call it does in fact aglSetCurrentcontext( _aglContext ), where > _aglContext != NULL.
It could be that your Cocoa NSGL stuff is doing things with the context. Can you attach with the OpenGL Profiler and check 'Break on Error' and 'Multithread Control Force On' (both in the Breakpoints window)? > 18081 2959212544 //Users/slate/Documents/equalizer/XCode/../lib/ > client/ > aglWindow.cpp:367 237 Created AGL context 0x290b2200 shared with 0 > 18081 2958110720 //Users/slate/Documents/equalizer/XCode/../lib/ > client/ > glWindow.cpp:169 237 Window drawable config: GL2.1|DB|st8|rgb8|a8 At least during initialization you've got a valid GL context with a reasonable pixel format... I couldn't spot anything else in the log, but obviously your context gets unbound or deleted. Does it work with config.egc, which is using only one window? > Which doesn't make sense to me because Carbon shouldn't be OBJC > objects, yeah? It's all C++ stuff, which is why you have to do > `Global::enterCarbon();`? The Carbon lock has a different reason. Parts of the Carbon API used by AGLWindow are not thread-safe, which is why we have to lock them during initialization. HTH, Stefan. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
