Zugg Software :: View topic

Beginner Joined: 31 Jul 2006 Posts: 18

I have a few questions about using mxp, specifically the #MXP command.
Consider some mxp test code I wrote:

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

#1 I'm not sure about. I notice the same thing, so I assume it's related to open/secure stuff that I'm both not as familiar with and which I generally don't have to worry about (as I don't play on an MXP-enabled mud.)

#2 is probably intentional, at least for the moment if not for all time. The MXP support in ZMud was basically taken straight from ZMud, without very many modifications and upgrades. Most of it predates any work Zugg put into inline images, but I'm not sure if he can or plans to upgrade MXP to allow for the same (ie, <HR> and inline <img> stuff). It's probably related to the fact that Zugg's been chronically optimizing his product for text scrolling rather than graphics.

#3 I'm not sure if it actually works, but it's generally a tag to preserve user-written formatting. Kinda like [code] tags on the forums.

#4 seems like it's just you. Of course, it's much easier just to leave off the arg names...

#5 is due to a bug. If it's fixed, the version it's fixed in isn't released yet.

Beginner Joined: 31 Jul 2006 Posts: 18

Figured out what was going on with the <send>, both of these work:

#MXP <send "command" hint~="command popup">command</send> <nobr>

#MXP {<send "command" hint="command popup">command</send> <nobr>}

Just the equals sign getting mangled but you are right, it is easier to leave off arg names.

Thanks for the feedback.

By the way are there any plans to highlight mxp tags in the syntax editor?

Posted: Mon May 07, 2007 5:33 pm

No plans to highlight MXP tags since MXP tags are not a normal part of most CMUD scripting.

#1: The #MXP command sends the line to the screen in MXP "secure" mode. When you send a
, it starts a new line and the new line is now in Open mode, so that's why it doesn't get recognized. Since you can display blank lines just using the #CR command, you don't need to use the #MXP command to do this. Or, you can put a %e[1z sequence to switch back to Secure mode on the second line.

#2: The HR tag currently isn't implemented. But you could use the IMG tag to display a line graphic if you wanted

#3: Should be the same as the TT tag. It selects a non-proportional font to preserve user formatting.

#4: Regarding your second post: You should always put {} around your entire MXP string when using the #MXP command for it to parse correctly.

#5: Yes, as Matt mentioned, this bug should be fixed in this week's release. (hopefully tonight)

Beginner Joined: 31 Jul 2006 Posts: 18

I reworte my test code to:

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

The curly brace thing is a little odd too.
A very simple example.

#alias isHere {$text={A <send 'Greet %1|Kick %1|Punch %1' 'Greet|Kick|Punch'>%1</send> is here.};#mxp $text}

Note in this case I did NOT use the curly braces with the #MXP command. If you do so it fails.

Also, if you try this with a normal variable it will not work unless you use #execute {"#mxp "@text}