FROM : R. Scott Thompson
DATE : Thu Dec 09 20:46:00 2004
> I haven't tested this, but you could try using an NSColor that is not
> equal to [NSColor blackColor], but whose RGB components are 0. I
> believe it is sufficient to use
> colorWithCalibratedRed:green:blue:alpha: but if necessary you could
> use a custom NSColor subclass.
BAH!!! I found a bug in my test code. It turns out that this DOES
work, (using a separate instance of black created with
colorWithCalibratedRed...).
As it turns out, however, if you then round-trip that same code through
RTF (that is, you generate an RTF from it, and then generate a string
from the RTF) you loose all the lovely work you did in applying your
own black to the ranges.
That is what I would expect to happen... it's not what I want to happen
in this particular case... but it seems like the Right Thing™ to do.
Scott
DATE : Thu Dec 09 20:46:00 2004
> I haven't tested this, but you could try using an NSColor that is not
> equal to [NSColor blackColor], but whose RGB components are 0. I
> believe it is sufficient to use
> colorWithCalibratedRed:green:blue:alpha: but if necessary you could
> use a custom NSColor subclass.
BAH!!! I found a bug in my test code. It turns out that this DOES
work, (using a separate instance of black created with
colorWithCalibratedRed...).
As it turns out, however, if you then round-trip that same code through
RTF (that is, you generate an RTF from it, and then generate a string
from the RTF) you loose all the lovely work you did in applying your
own black to the ranges.
That is what I would expect to happen... it's not what I want to happen
in this particular case... but it seems like the Right Thing™ to do.
Scott
| Related mails | Author | Date |
|---|---|---|
| Douglas Davidson | Dec 9, 19:34 | |
| R. Scott Thompson | Dec 9, 20:06 | |
| R. Scott Thompson | Dec 9, 20:46 |






Cocoa mail archive

