Re: CGContextSetRGBFillColor() off by one?
Re: CGContextSetRGBFillColor() off by one?
- Subject: Re: CGContextSetRGBFillColor() off by one?
- From: "Ken Ferry" <email@hidden>
- Date: Sat, 31 May 2008 22:01:52 -0700
Thanks for the pointer. :-)
If the device colorspaces were just generic ones, my test program would work.
I heard back on my bug, though. Indeed, the device spaces are no
longer device dependent. The device RGB space at least at the moment
coincides with the colorspace of the main display.
(The urging in the docs is that you replace usage with a generic
space, not that device and generic spaces are the same.)
Anywho, just to close up, yes, you're seeing color transformation.
Fill with a color that's already in the destination colorspace to
avoid it.
-Ken
On Fri, May 30, 2008 at 5:15 PM, Michael Vannorsdel <email@hidden> wrote:
> 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 (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
>
_______________________________________________
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