• 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: CGCaptureDisplay behaviour
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CGCaptureDisplay behaviour


  • Subject: Re: CGCaptureDisplay behaviour
  • From: Ryan Pettigrew <email@hidden>
  • Date: Tue, 6 Apr 2004 16:09:29 -0400

Just to make sure this gets the attention this deserves, since I also have many questions about this functions behavior, Ive also sent a copy to the Quartz-dev list. If this kind of cross-posting is improper conduct, please let me know, and I will refrain from doing it in the future.

Hi,

I have a problem when using CGDisplayCapture on a non-main display. When I do this, starting at MacOS 10.3, it is not possible to switch back to any other application but it is possible to click and manipulate windows from the Finder or other apps. Keyboard events are also not passed to other apps. I would understand this behaviour when capturing the main display, but why the hell this happens when capturing another display?

The reason why we need to do that is because we have a video broadcasting app that needs to draw in realtime on display #2 but it is NOT a game that requires locking the user in it.

Has anybody experienced the same symptom and is there a solution?


Thanks,


Daniel Tapie

I am also puzzled as to why a screen capture operation disables things that are completely not screen related (such as system related keystrokes, and whatnot). Shouldnt that operation be up to a separate function? I realize that Apple wants to make it easier for developers to bypass the system and do their own thing, but for some things, that is just overkill (like in a shareware game). What Cocoa features are maintained when the screen is captured? Is there any way to return default Cocoa features to this full screen state? Is there a separate function which captures the screen, but keeps Cocoa features, such as Quartz drawing and Cocoa keystrokes?

Ryan Pettigrew
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Re: [little OT] Licensing/Implementing in Cocoa/Obj-C
  • Next by Date: Re: Lost IBOutlet.
  • Previous by thread: CGCaptureDisplay behaviour
  • Next by thread: NSMenu update problem
  • Index(es):
    • Date
    • Thread