| Message |
Maybe the documentation is slightly wrong. I found this in another post:
OnPluginMXPstart
OnPluginMXPstop
OnPluginMXPopenTag
OnPluginMXPcloseTag
OnPluginMXPsetVariable
OnPluginMXPerror
OnPluginMXPopenTag
It seems that in the case of OnPluginMXPopenTag it the callback expects a single argument in the form:
name,arguments
In other words, you would get something like this:
sound,FName="mm_door_open.*" V=100 L=1 P=50 T="misc"
Thus you could use Split to break up the line into "sound" and the arguments, and then proceed much the same as before.
OnPluginMXPcloseTag
Just to complete the documentation, in the case of OnPluginMXPcloseTag you get the tag name followed by the text of the tag. eg.
<b>Hi there</b>
In this case the close tag for "b" would have as its argument:
b,Hi there
OnPluginMXPsetVariable
For OnPluginMXPsetVariable the argument is variable name=value, eg.
RoomName=Red Square
OnPluginMXPerror
For OnPluginMXPerror the argument is:
level,number,line_number,message
eg.
I,10008,417,MXP mode change from 'open' to 'permanently secure'
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | top |
|