I don't suppose, in a future version, there could be a mode whereby there are two output screens, one with the MXPised screen and one with the output showing all the tags?
It'd be awfully handy for debugging.
It'd be awfully handy for debugging.
Dupe screen feature
Posted by Ian Kirker on Sat 07 Aug 2004 10:18 PM — 5 posts, 22,563 views.
Turn your MXP debug level to "The Lot". Everything gets output in a separate notepad window.
I mean all the tags in context, as in, what you would see if the MUD was sending tags with your text and MUSHClient wasn't interpreting them.
Then you essentially want to be able to 'view source' on the MUD.
Clarity helps.
Clarity helps.
You could use "debug packets" and then youd see everything. Which, if you were debugging, would come in handy, albeit a little unweildy at times.
If you just want to see the tags, you can turn MXP off clientside, then MC wont interperate tags.
Although, I will say this is hardly a side by side as you want.
We can currently open a new window (Windows > New Window) and youll duplicate the output and stuff, but then the only thing you can do to each independantly is pause it.
It would make sense to be able to turn one into a raw mode. However, this would be a coding nightmare, since first you'd have to figure out how 'raw' you wanted, with ANSI being interpreted or not, and then you'd have to deal with lines being different lengths, and deal with plenty of other descrepencies.
Debug Packets might be your best bet... Or actually, you can probably whip up a quick script with plugin callbacks to write everything to a text file (FSO), considering you wont need color, or anything, that should be sufficient.
If you just want to see the tags, you can turn MXP off clientside, then MC wont interperate tags.
Although, I will say this is hardly a side by side as you want.
We can currently open a new window (Windows > New Window) and youll duplicate the output and stuff, but then the only thing you can do to each independantly is pause it.
It would make sense to be able to turn one into a raw mode. However, this would be a coding nightmare, since first you'd have to figure out how 'raw' you wanted, with ANSI being interpreted or not, and then you'd have to deal with lines being different lengths, and deal with plenty of other descrepencies.
Debug Packets might be your best bet... Or actually, you can probably whip up a quick script with plugin callbacks to write everything to a text file (FSO), considering you wont need color, or anything, that should be sufficient.