Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'It worked, now let's improve it.' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
It worked, now let's improve it.
Authored by: Bishop on Mar 28, '02 10:19:10AM

I've tried it and it worked fine. One problem tough it didn't get as bright as I wanted, no real improvement. Would it not be possible to change the color to something like [0 1 1 1] to get a cyan color instead? I don't have all the stuff to figure out exactly how to change this, but shouldn't something like:

lfs f4,21784(r9)
fmr f3,f4
fmr f2,f3
fsubs f1,f2,f3

do this? Also would it not be nice if someone sat down and wrote a patch that did this "automaticly"?



[ Reply to This | # ]
It worked, now let's improve it.
Authored by: dete on Mar 29, '02 07:43:21PM

I don't know if going with cyan would really be an "improvement", if you just want cyan text, then you can simply remap the colours the way that greygent suggested.

It's true that the "lighter" blue that I was able to achieve is still a little darker that is ideal. In my testing I found (0.3, 0.3, 1) to be better, but I couldn't find a way to calculate 0.3 in just 4 instructions (you can't increase the number of instructions without breaking the whole application.)

I also thought that it would be nice to be able to work out different colours for bold vs. normal text. It turns out that Terminal stores two colour objects, one for bold text, one for normal text, but then initializes them to the same value. You could use slightly different shades to indicate bold colours...

As for building a patch tool, I would only consider it if I could figure out a way to specify all colours explicitly. Anything less is just "much ado about nothing"... (Plus the patch would only work on one version of Terminal.app.)

Cheers,
-dete



[ Reply to This | # ]