At the moment, the MXP port of Mudlet doesn't seem to respect or support the use of PROMPT in <send> tags. At this time, it sends the string in the link to the MUD as normal instead of to the command line for more information to be added. I'll be glad to answer any questions, and if you require an example of the MXP tags being sent, I'll be happy to provide one.
Thank you.
[bug/feature request] MXP <send> prompt support
Re: [bug/feature request] MXP <send> prompt support
Can you provide an example?
Re: [bug/feature request] MXP <send> prompt support
I think Lusternia might be making use of this, though I'm not sure.
Re: [bug/feature request] MXP <send> prompt support
<send href=\"admin gedit 1234 Name \" PROMPT>Name:</send> imperial <send href=\"admin gedit 1234 ShortDesc \" PROMPT>Short Desc:</send> a plump imperial
Re: [bug/feature request] MXP <send> prompt support
What is supposed to happen here?
Re: [bug/feature request] MXP <send> prompt support
As copied from: http://www.zuggsoft.com/zmud/mxp.htm#Links<SEND> to command line
To send text to the client's command line instead of sending it directly to the MUD, use the PROMPT argument in the <SEND> tag.
Example: <SEND "tell Zugg " PROMPT>Zugg</SEND>
will put the text "tell Zugg " (without the quotes) into the command line when the "Zugg" link is clicked.
(Sorry for the link, but it's the only mxp documentation I could fine on short notice)
Re: [bug/feature request] MXP <send> prompt support
OK. This can be added.
Re: [bug/feature request] MXP <send> prompt support
Sorry to resurrect an old thread, but I had a couple MXP requests/questions, and this seemed to be the perfect place for them.
This is a major part of my OLC, as the builder can click links like "name" and "description", and then when sent to the command bar, they can immediately begin entering the string. According to this thread it "can be added", will it?
I use the &text; variable in 99% of my MXP, as it cuts down largely on having to throw duplicate arguments into functions, and saves on bandwidth. Is this on the agenda for MXP?
This is a major part of my OLC, as the builder can click links like "name" and "description", and then when sent to the command bar, they can immediately begin entering the string. According to this thread it "can be added", will it?
<SEND> to command line
To send text to the client's command line instead of sending it directly to the MUD, use the PROMPT argument in the <SEND> tag.
Example: <SEND "tell Zugg " PROMPT>Zugg</SEND> will put the text "tell Zugg " (without the quotes) into the command line when the "Zugg" link is clicked.
I use the &text; variable in 99% of my MXP, as it cuts down largely on having to throw duplicate arguments into functions, and saves on bandwidth. Is this on the agenda for MXP?
This would display the text "bread" and "water" and send the appropriate "buy" command when they are clicked. To minimize the text sent by the MUD in this case, it would be easier to set up your own Element for the store. For example:
<!ELEMENT Item '<send href="buy &text;">'>
<Item>bread</Item>
<Item>water</Item>
Re: [bug/feature request] MXP <send> prompt support
Which MUD is this on? I've added support for this, but I found only one MUD where I could test this with. The patch is available @ https://bugs.launchpad.net/mudlet/+bug/1077548