Zugg Software :: View topic - [3.12] Mxp, style coloring, specificly can't turn it off?

Apprentice Joined: 01 Dec 2006 Posts: 178

As it is, I can't seem to find a way to disable the style that makes it so that mxp links are made a specific color

I want to remove the style coloring because my mxp stuff already has its own coloring, but I seemingly can't? I can remove the underline.
But I can't tell it to keep the color it gets from the mud, though if I capture it it shows the right color.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

The underline is a %pref()-only option now. It used to be in the Preferences window, but Zugg decided to unclutter that. Don't know about the coloring, though.

Apprentice Joined: 01 Dec 2006 Posts: 178

Yeah I've removed the underlining but cmud is still aplying its own color to the mxp making it gray, rather then the color it actually had.

Wizard Joined: 22 Mar 2007 Posts: 2320

Did you adjust the Preferences? Click on Options|Colors. In the Global Styles window, click to open the Session folder. Click on the URLs style. Change the text color and apply. (The option to underline is also there.) Is this what you tried?

Wizard Joined: 22 Mar 2007 Posts: 2320

Oops, I misread what you wanted. You don't want to change the color, you want it to stop changing the color and use the color the mud sends. I don't believe there is a way to do that. The best you can do is set it to be what you expect the mud to be sending.

Posted: Mon Dec 07, 2009 9:34 pm

In the Prefs/Styles/URLs style page, you can prevent the color by setting the Text color to "Default".

But CMUD doesn't normally give any color to MXP links...it only underlines the links. So if your links are showing up in a specific color, it's possible the MUD itself is sending the COLOR tag. You'd need to turn on the Raw Input option in the Script Debugger window to see the raw text sent from the MUD to see what MXP commands are actually being sent.

Apprentice Joined: 01 Dec 2006 Posts: 178

well its on default right now and it still colors them to 'gray'
But as said if I capture it to show in another window it shows up with the right colors..

The one to the left, is the main window, the right one is the captured result going into my 'map' window
the colors are right in the captured one but not in the main window one
and url's are on default but it doesn't keep those colors, the code received for that is.

Posted: Tue Dec 08, 2009 7:35 pm

Your MUD is sending a custom MXP tag (the "mpelm" tag). So it's not sending a plain URL link (using the A tag). You can check in the MXP Preferences to see what the Element definition of the "mpelm" tag is, but my guess is that the MUD is setting it to a specific color. But I'd need to see the full !!ELEMENT tag that is being used when you connect to the MUD to define this tag.

The reason the color doesn't transfer when you send it to the capture window is probably because you have the "Capture MXP" option turned OFF for that window. That prevents any transfer of MXP tags. Since the colors are being set by the ANSI control codes in the capture above, the color works in the capture window because there isn't any MXP tag.

In general, this MUD is doing something pretty complicated and is mixing ANSI color codes within MXP tags, which is not recommended. Once I can see the definition of the "mpelm" element, I might be able to fix it though.

Apprentice Joined: 01 Dec 2006 Posts: 178

incidently capture mxp is set to on
And all this worked fine in 2.37

it showed colors right and everything, this is a problem that has only arrived after I switched over to the beta.

It is not aetolia that is sending this code for the map, but mudbot, a proxy program for ire games for mapping, it generates this map and has worked without any single problems until now.

Going to install 2.37 again and see if it wants to play along.

Apprentice Joined: 01 Dec 2006 Posts: 178

ok I just ran 2.37
and it worked just fine in the coloring when 'default' was selected, however in 3.18 default does not get applied right...

in 3.18 it defaults to grey, the one shown in the image, rather then the color the mud says.

Posted: Wed Dec 09, 2009 5:26 pm

Like I said, I need to see the definition of the "mpelm" tag before I can help with any of this. It's certainly possible that it's a v3.x bug, but without the definition of "mpelm" there is nothing I can do. Even with mudbot you should be able to see the definition in the script debugger window when you connect to the mud.

Apprentice Joined: 01 Dec 2006 Posts: 178

Posted: Thu Dec 10, 2009 5:46 pm

I have reproduced the problem. It seems to be an issue when using ANSI color codes within a MXP SEND tag. I've added this issue to the bug list.