 |
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
 Posted: Sun Apr 05, 2009 9:40 pm
[3.05] Why aren't the MXP and #cw colorings the same?
|
When I print out brown through MXP and through #CW they are different in color. Is this a bug?
Run 'runme' from the xml code below:
| Code: |
<class name="test_color" id="3430">
<alias name="runme" id="3428">
<value>#say %crlfBrown through MXP
#say Brown through ~#cw</value>
</alias>
<trigger priority="34290" case="true" regex="true" id="3429">
<pattern>^Brown through \#cw</pattern>
<value>#cw brown</value>
</trigger>
</class>
|
My follow-up question is, how do I make them the same? |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sun Apr 05, 2009 10:01 pm
|
I think your script is incomplete, but it was pretty easy to demonstrate the issue.
This problem results from "brown" having different definitions. "Brown" in MXP means the HTML colour brown (#A52A2A), whereas in #cw it means the ANSI colour brown (#808000, it's actually the un-highlighted yellow colour). To use the MXP brown with CW, you need to use the keyword "mxpbrown" instead, or you could just use the hex codes. |
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Sun Apr 05, 2009 10:05 pm
|
Thanks Fang. Would the opposite be possible as well? With MXP color capturing to windows still bugged I need to use ansi colors until its fixed. Is there a way to specify the ansi brown for the mxp statement?
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Apr 06, 2009 6:58 pm
|
Nope, sorry, MXP doesn't know anything about ANSI color names.
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Mon Apr 06, 2009 10:04 pm
|
But you can use the hex code, which I provided above ;)
|
|
|
|
|
|
|
|
