Re: Capturing the right display, but rendering to the wrong one.
Re: Capturing the right display, but rendering to the wrong one.
- Subject: Re: Capturing the right display, but rendering to the wrong one.
- From: David Duncan <email@hidden>
- Date: Mon, 17 Sep 2007 13:29:29 -0700
On Sep 17, 2007, at 11:56 AM, Karan Lyons wrote:
Thankyou, but I don't think it's an issue with Quartz Composer.
I'm pretty sure that it's an issue with the code I modified,
specifically the way the openGL context is created. I've attached
the project as a zip file to this email if anyone wants to look at
the whole thing. To see the issue you need to have at least two
monitors.
What should happen is that the application will run, the secondary
monitor will blank out, and the primary monitor will show the
"Rings" composition from the developer examples. As the primary
screen has not been captured, there will be a lot of screen
refreshing issues.
If there's any more information you need, I'll be more than happy
to supply it.
It looks like your setting up your attributes array before you
discover what display ID the secondary display is. Try updating your
attributes array (and delaying the corresponding creation of the
pixel format) until after you've discovered the ID of the secondary
display.
--
David Duncan
Apple DTS Quartz and Printing
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden