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 (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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
