Zugg Software :: View topic

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

anyone else noticed MXP subs not being underlined in versions above 7.05? Not sure which it turned up in, current is 7.13b. I have toggled the setting, closed/opened, retoggled, closed/opened zmud but to no avail.

#MXP <send "text">text</send> is underlined.. but when using in a #SUB this is no longer the case.

#TRIGGER {^(%w) just sent you a tell.$} {#SUB {<send "replay">%1 just sent you a tell.</send>}}

works.. i can still click it and it send replay.. but no underline.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Odd, I get the underline using 7.13b
I wish I didn't though (or that I could remove it), it's irritating. Maybe we can swap installs ;)

Don't suppose you know of a way to still highlight text that's got an MXP trigger on it? I've got some things highlighted (using #CW) in one trigger and MXP in another, but I lose the highlights when MXP kicks in...

Wizard Joined: 14 Oct 2000 Posts: 1368

Check View->Preferences->General->MXP->Underline MXP Links

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

i use

#SUB {%ansi(high,red)<send "north">north</send>}

to color MXP tags... i think there is a tag for color... <font color=red></font> ??

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Another odd thing actually with MXP (trying to keep it to one topic)

A trigger for communications...

#SUB {<C #1111EE>%1 Shouts: %2</C>}

works fine

however, this doesn't work if the #SUB is inside an #IF statement...
(assume %1 is Guinn, %2 is hello)

#if (x=1) {#SUB {<C #1111EE>%1 Shouts: %2</C>}}
#if (x=2) {#SUB {<C #1111EE>%1 Whatever: %2</C>}}

And if x=1 the output becomes
C #1111EEGuinn Shouts: Hello/C

if x=2
C #1111EEGuinn Whatever: Hello/C

Maybe I'm missing some brackets, or the <> is forcing an expansion rather than working as it should?

Posted: Wed Aug 24, 2005 11:37 am

I think in an #if #sub combo you need to use %ansi.
At least that's what I do

Trigger:
^You lost your concentration while trying to cast (*).

Pattern:
#IF (%ismember( %1, @spellup_yeslist)) {
#SUBSTITUTE %ansi(high,yellow)"Ya screwed up trying to cast %1. Recasting."
%1
} {#SUBSTITUTE %ansi(high,yellow)"Ya screwed up trying to cast %1."}

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

Did anyone test this and does it underline on your system?

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Anyone tried using ~ like the helpfile shows:

Using MXP in the #SUBSTITUTE command

Instead of using the #MXP command to send Secure MXP commands to the screen, you can also create a trigger and then use the #SUBSTITUTE command to add MXP commands to the text. For example,

#TRIGGER {north} {#SUB {~<send>north~</send>}}

will replace the word "north" whenever it is displayed by the MUD and replace it with the text <send>north</send> which creates a hyperlink. If you click on the "north" hyperlink, the command "north" is sent to the MUD.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The use of tildes as the help file suggests is something I put in since "Use <> for expansion" is on by default, and my experience with the forums suggested it would elminate a number of questions. Following that statement in the help will never hurt, and would help in Guinn's case. Private's problem is something completely different. I would do some testing with it, but I still haven't updated from 7.05. My tests with that version worked. and I don't see anything indicating Zugg tweaked with either MXP or the display between 7.05 and 7.13b

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

the use of tildes IS required from the command line when entering a trigger from the command line, thus why i posted pattern and value in the 1st bit of code... and the second is only a #SHOW so it NEEDS to evaluate the <> as an mxp tag.

So no nexula.. i dont need the tildes as im not enternig the trigger from the command line. You took the example in the help a liitle to broad.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

i tracked down what was wrong... in my status window i had the 2 following bits...

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

as a side note, i made another post concerning MXP and colors using #SUB, where the colors would bleed across several MXP sends inside a single sub, this problem has now magically cured itself too :)