Re: __CGPixelAccessLockWindowAccess???
Re: __CGPixelAccessLockWindowAccess???
- Subject: Re: __CGPixelAccessLockWindowAccess???
- From: Michael Watson <email@hidden>
- Date: Thu, 21 Jun 2007 16:28:57 -0400
Fair enough, but when the OP doesn't post any code and assumes a
framework bug, I get skeptical. :-)
--
m-s
On 21 Jun, 2007, at 16:05, Finlay Dobbie wrote:
In fairness, if an internal framework function is reporting a
parameter error, that's probably a bug in the framework. I doubt the
OP is calling the function directly.
On 21/06/07, Michael Watson <email@hidden> wrote:
It's probably /not/ a problem in the OS frameworks, honestly. They're
not 100% bulletproof, but they're well-tested. When my applications
don't work correctly, it's almost always my fault.
You should probably post relevant portions of your code to the list.
--
m-s
On 21 Jun, 2007, at 13:54, Stephane wrote:
> I think I've found the origin of the bug. It's probably in the OS
> frameworks as I don't think it's forbidden to do what I'm doing.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
40gmail.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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