I was wondering what is up with the new colour on mIRC 6.1 at 16 (some dark green colour), and I'd like to know why all the colours above 16 (17, 18, 19, etc.) were changed to default colour.
I know people will say "you don't need those colours, just stick with the default 0-15", please spare me that.
very interesting.
For many people, ^k16 now looks like a muddy gray-green-blue $rgb(66,97,99)... while other people see white or black.
I guess this could be an indication of extended color support in the future, but currently see no way to modify this palette currently (by editing the mirc.ini or otherwise).
Very cool though!
would be nice to have added color selections .. but i think khaled said he wasnt planning this in a post earlier tonight .. altho id have to search for it .....
I'd like to see added colours selections too and I have been nagging for years for it.
For many people, ^k16 now looks like a muddy gray-green-blue $rgb(66,97,99)... while other people see white or black.
Perhaps this would depend on a users colour settings as this colour would probaly fall outside the 16 colour or maybe eveb 256 colour range.
those RGB values were taken under 24bit color mode.
under 16bit color mode, the values are 63,95,95.
This is the same for everyone who can get the gray-green-blue color, where as it seems others still get color 0 for 16.
What OS are you running? Maybe this is an issue with mIRC initialising an integer at a weirdish number on some systems (Khaled is using a new compiler after all). Although it's kind of bizzare that it only effects colour 16 and none of the other 'vacant' colours, and that it only seems to be one colour (two if you count the 24 and 16 bit display difference pointed out above) and not a diverse range of colours one would expect given different systems configurations. To the technically savvy: when a variable is initialised with 'garbage' is it the same garbage all the time?
Maybe this is an easter egg?
I show that color with win95b (yes, it's STILL being used (referencing another thread - (sarcasm) I guess if MS decomishioned it that means most viruses wont bother it anyomore?? LOL)) for CTRL+K 16 and 17+ (for me) show the same as 11. my video card (albeit an OLD one) is set for True Color (24 bit) which is 2 settings HIGHER than 256 colors (as somebody originally pointed out COULD be the case with the new color)
[color:426163]
Maybe this is an easter egg? 66 97 99 == "Bac"
63 99 99 == "?cc"
Hmm, I can't really think of anything else to try.
It's a nice color though. Very mellow; more character than gray without calling too much attention to itself.
(landonsandor): it's quite a bit darker than 11, and 10 for that matter.
[/color]
//echo -a 1,1 x 16,16 x 10,10 x 11,11 x 
Ok, try this: //echo -a 1,1 x 16,16 x 10,10 x 11,11 x 17,11 x 18,11 x
That's what I was refferring to with the 17+ comment; 17+ (didnt try them ALL mind you) are all the same color (for me) as 11. I LIKE the new 16 color - kinda like a smoked grey.
EDITED
Side ntoe, in the above example, 17,17 and 18,18 didnt work for me - they showed no backround
In any case I see it as Black so I feel left out. :tongue:
As you should. :tongue: :tongue:
Don't feel left out. I get black too in 32 and 16 bit...
It seems more like a bug, because transparent (99) doesn't work anymore.
K99 isn't transparent as such, what it does is revert to the standard event setting for a given event and it seems to be working for me at the moment.
I see 16 as black also. You sure you ppl dont have a theme set other than default?
absolutely. Even pressing the reset button.
To the technically savvy: when a variable is initialised with 'garbage' is it the same garbage all the time?
The answer is "maybe" it would depend where the garbage is coming from. Usually (I'd say maybe 99% of the time), if you reboot the system and try again, it should give you different garbage. However, the fact that it is happening on different systems, with different configurations makes me think it is not garbage because surely different people would have different stuff in their RAM. However personally, I just see black for color 16.
*sighs* misread a reply *deleted*
It's black here too; however, while
/echo -a 16test
displays the text black on white,
/echo 16 -a test
displays it white on white! And yes, so do 17 and higher, up to and including 98, 99 becomes black again. Some quick tests show that all this is not dependent on the background colour.
The plot thickens...