This is from the CGColorSpaceCreateDeviceRGB docs:
In Mac OS X v10.4 and later, this color space is no longer device-
dependent and is replaced by the generic counterpart—
kCGColorSpaceGenericRGB—described in “Color Space Names”. If you use
this function in Mac OS X v10.4 and later, colors are mapped to the
generic color spaces. If you want to bypass color matching, use the
color space of the destination context.
So since 10.4 the device colorspaces are now just generic ones.
On May 30, 2008, at 1:38 PM, Ken Ferry wrote:
Well... I'm not sure that's true any more is it? I mean, don't all
the
DeviceXXX colour spaces get mapped to the new "Generic" ones as of
10.4?
I don't believe so, and that isn't what I see in testing.
I filed a bug for this yesterday. My understanding, which may be
flawed, is that using a 'device' colorspace is a pledge that you know
that your color components are already with respect to the colorspace
of the destination, so require no further color correction.
_______________________________________________
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 [EMAIL PROTECTED]
