• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Capturing the right display, but rendering to the wrong one.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 09:53:26 -0700

On Sep 15, 2007, at 4:25 PM, Karan Lyons wrote:

I'm trying to modify the Performer Application in the developer examples to capture a secondary display if it's attached, and then render to it. I can capture the secondary display, but the qtz file still renders to the main display. I think it has to do with the openGL Context that I'm creating, but I don't know what to change to fix it. The code is attached. I'm sure the solution is simple, I just can't figure out what it is.

This would probably get a better answer from the quartzcomposer-dev list, but I think the issue might be related to other multi-context issues that are known in Quartz Composer on 10.4. It would help if you could file a bug on this and send me the bug number.
--
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


References: 
 >Capturing the right display, but rendering to the wrong one. (From: Karan Lyons <email@hidden>)

  • Prev by Date: Re: Sharing a view between NSWindow instances
  • Next by Date: Re: CoreData Indexing is it possible?
  • Previous by thread: Capturing the right display, but rendering to the wrong one.
  • Next by thread: Re: Capturing the right display, but rendering to the wrong one.
  • Index(es):
    • Date
    • Thread