Hi, FYI, I have some working code without the use of CGLMacro.h, but I generally save the current context before setting mine and restore it just before leaving the drawing method. Best,
Raphael www.creaceed.com On Fri, Apr 25, 2008 at 6:58 PM, vade <[EMAIL PROTECTED]> wrote: > Hello > I am trying to debug some odd behaviour in my custom QC patch. I am not > using CGLMacro.h, but I am doing the following to set the current GL > Context: > > CGLContextObj cgl_ctx = [pluginContext CGLContextObj]; > CGLSetCurrentContext(cgl_ctx); // work around lack of GLMacro.h for now > > > > I am aware that there is a slight performance hit due to the setting of > the context and the needed lookup, but I am wondering if setting cgl_ctx > using the macros is *required*. Im 95% sure my issue is due to me using some > quasi functional GLSL stuff, but for example my plugin renders white if I > stop and start the rendering in the QCeditor, and only returns if I force > fullscreen and back. I also loose the mouse cursor - it becomes this really > lovely glitched out square... until I trigger the cursor to change by doing > something like clicking a text field. > > Thanks for any clarification. > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > > http://lists.apple.com/mailman/options/quartzcomposer-dev/raphael.sebbe%40gmail.com > > This email sent to [EMAIL PROTECTED] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
