On 30 May 2008, at 02:21, Ken Ferry wrote:
Well, if you use CGContextSetRGBFillColor as you said, then that sets
a device RGB colorspace up as the fill colorspace, and device
colorspaces don't do color matching. Device means 'untagged'. Which
is to say, I don't know, sounds strange.
Well...
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
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
Hi there,
I have this code:
CGContextSetRGBFillColor(cref, 0xaa/255.0, 0xb0/255.0,0xc0/255.0, 1) ;
CGContextFillRect(cref, CGRectMake(0, 0, w, h)) ;
CGContextFlush(cref) ;
Later on, I get the image buffer to print out the contents of the
first pixel:
Am 29.05.2008 um 09:21 schrieb Mike Manzano:
Regardless of what I set the red component to, the value in the
actual image buffer is always off by one (it is always exactly one
less). This does not seem to be true for the green and blue
components.
Any ideas why?
ColorSync hard at
I just tried running it on an old PowerBook, and I get the same
results. Do you know for sure that ColorSync is in play here?
Thanks,
Mike
On May 29, 2008, at 2:40 AM, Uli Kusterer wrote:
Am 29.05.2008 um 09:21 schrieb Mike Manzano:
Regardless of what I set the red component to, the value
Well, if you use CGContextSetRGBFillColor as you said, then that sets
a device RGB colorspace up as the fill colorspace, and device
colorspaces don't do color matching. Device means 'untagged'. Which
is to say, I don't know, sounds strange.
Try asking on Apple's quartz-dev list.
-Ken
On Thu,
Am 29.05.2008 um 23:17 schrieb Mike Manzano:
I just tried running it on an old PowerBook, and I get the same
results. Do you know for sure that ColorSync is in play here?
No. It just seemed like the most likely culprit to investigate,
because by definition, a color correction system must
After playing with it some more I think it might be a floating point
precision error.
On May 29, 2008, at 9:40 PM, Uli Kusterer wrote:
Am 29.05.2008 um 23:17 schrieb Mike Manzano:
I just tried running it on an old PowerBook, and I get the same
results. Do you know for sure that ColorSync
