 |
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
 Posted: Mon Aug 13, 2007 11:21 pm
[1.34]#MXP %ansi bug
|
When I use this command:
#MXP %ansi(high,red)One big %ansi(white)black
it displays
%ansi(high,red)One big black
where only the last word has the correct color.
But if something else is written before the first %ansi, it is displayed correctly.
I think this is a bug. |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4690
Location: Pensacola, FL, USA
|
Posted: Mon Aug 13, 2007 11:39 pm
|
When using #MXP you have to use MXP color syntax.
#MXP {<COLOR RED>One big</color><color white>black</color>} |
|
_________________
Discord: Shalimarwildcat |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Aug 14, 2007 1:35 am
|
Also, the original problem with your #MXP command is that you had a space in it. You need {} around the argument to #MXP in CMUD.
Shalimar is correct though...you shouldn't be using ansi colors in MXP. |
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Wed Aug 15, 2007 9:30 pm
|
Is that only if you use the MXP command? Because this works perfectly fine.
#say %ansi( red)~(%ansi( yellow)Notice%ansi( red)~)%ansi( gray): <color white navy>%expand( %-1)</color>%ansi( gray) |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Aug 15, 2007 9:31 pm
|
Yep, the parsing problem is only with the #MXP command.
|
|
|
|
|
|
|
|
