Brad, I dug into DVD Players symbols and it would appear to be using private API of the Core Graphics Services variety. http://cocoadev.com/wiki/CoreGraphicsPrivate
Specifically CGSSetWindowCaptureExcludeShape() Hope this helps. -Richard On 06/03/2013, at 11:06:59 PM, Scott Ribe <scott_r...@elevated-dev.com> wrote: > On Mar 6, 2013, at 10:21 PM, Brad O'Hearne wrote: > >> ...but they do not get to call the shots or make the rules on how to use the >> content in the app... > > And there is the crux of my argument about fundamental stupidity. Once the > data is in the user's head, there is no technical means to control what the > user does with it. > >> Someone earlier mentioned DRM, iTunes, and the requirements of media >> publishers to secure such data. Different data, but same principle... > > Yes, and DRM is the classic and perfect example of the futility of trying to > simultaneously allow and disallow a user to access data. DRM is largely, and > quite famously, a miserable failure and vast waste of effort. (How many hacks > exist to capture DVD playback on OS X? Answer, in case you don' know: a lot, > and they're apparently damn near trivial to write.) > >> ...it is an absolute, non-negotiable requirement that data be secured in >> this way. I have zero ability to change that requirement. The requirement >> does not originate from me, nor is it mine to change -- it is only mine to >> solve. > > Well, that sucks... Are you 100% certain you have no ability to affect the > requirement? And what if the answer is "no, their is no way to do that on OS > X"? Or, more likely, what if the answer is "not through a supported API, only > by hacking the windowing system"? Is this misfeature really worth the all the > potential problems with conflicts and updates that come with injecting code > to modify kernel operations? > >> But even if I was given authority to make the call, I'd agree with the >> pursuit of this end -- this particular use case is a legitimate use-case for >> disabling screen-shots. > > Then you need to think about it more, rather than defending the indefensibly > stupid requirement handed down from marketing. > >> I'll refrain from any more attempts at explaining the scenario...I've said >> what I could, but if that still isn't enough, it shouldn't be too hard to >> imagine scenarios where this would be desirable. > > Unless you take time to think about it more deeply, in which case it becomes > obvious that the requirement is self-contradictory, and although someone > might indeed desire it, there is absolutely not, indeed cannot be, a scenario > where it is truly important. > > NB: thanks to friends/colleagues who work with truly confidential data, I > have a rough idea how the DOD & NSA deal with top secret data. I'm pretty > sure they would snicker at this "absolute, non-negotiable requirement" ;-) > > -- > Scott Ribe > scott_r...@elevated-dev.com > http://www.elevated-dev.com/ > (303) 722-0567 voice > > > > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/heardrwt%40gmail.com > > This email sent to heard...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
