Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput

Subject: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in -renderOutput
From: Matt Rhodes <email@hidden>
Date: Tue, 24 Feb 2009 10:52:18 -0800

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


Follow-Ups:

Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in	-renderOutput
From: Paul Schneider <email@hidden>
Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in	-renderOutput
From: Darrin Cardani <email@hidden>


Prev by Date:
Re: Importing XML to current project

Next by Date:
Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in	-renderOutput

Previous by thread:
Re: Importing XML to current project

Next by thread:
Re: FxPlug: renderInfo.sharedContext vs. CGLGetCurrentContext() in	-renderOutput

Index(es):

Date
Thread