Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput
Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput
- Subject: Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput
- From: Matt Rhodes <email@hidden>
- Date: Wed, 25 Feb 2009 12:00:26 -0800
This is Motion. I haven't checked FCP.
I'd like to know if there's a reason to use the current context in
Motion vs. the renderInfo.sharedContext.
Thanks.
m
On Feb 25, 2009, at 11:16 AM, Paul Schneider wrote:
Hi Matt,
Is this in FCP, Motion, or both? As far as I know, the contexts
should be the same in FCP.
- Paul
On Feb 24, 2009, at 12:52 PM, Matt Rhodes wrote:
Hey Team.
Can someone tell me the difference between the current context
(derived from CGLGetCurrentContext())
and renderInfo.sharedContext at the start of -renderOutput? From
what I can tell, they're different.
I realize renderInfo.sharedContext may be NULL when rendering to a
bitmap.
Thanks.
Matt Rhodes
Zaxwerks, Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden