Re: bad behavior from unlockFocus on 10.6
Re: bad behavior from unlockFocus on 10.6
- Subject: Re: bad behavior from unlockFocus on 10.6
- From: Ken Ferry <email@hidden>
- Date: Thu, 3 Sep 2009 12:54:36 -0700
Well, please file a bug with a test case that shows the behavior change. I
still think there's something else going on.
-Ken
Cocoa Frameworks
NSImage owner
On Thu, Sep 3, 2009 at 11:53 AM, Robert Clair <email@hidden> wrote:
> Hi Ken -
>
>
>> > This all worked fine until 10.6. The original NSImage object was left
>> unmolested.
>>
>> Nope. :-) Clearly you're seeing behavior change somewhere, but this
>> attribution is not correct.
>>
>> -[NSImage lockFocus] is a commonly misunderstood method. It is and always
>> has been lossy.
>>
>
> Not to be disputatious, but nope on your nope, for a couple of reasons:
>
> 1) If that were the case, the code wouldn't have worked for the last 5
> years.
>
> 2) The even better reason is that I just made a fresh build on a 10.5
> machine and stepped through it. The NSImage has the same single
> NSPDFImageRep after the -unlockFocus as it before the -lockFocus
>
> By accident I may have been relying on unintended behavior but it
> definitely worked before and changed with 10.6
>
> Bob
>
>
>
>
_______________________________________________
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