It is a limitation of the XML 1.0 specification that prohibits ASCII control characters (ASCII codes less than 32{dec} and delete 127) EXCEPT for <Tab> <CR> and <LF> - that prohibition also covers <ESC> so no putting ANSI Colour codes in your triggers though we have recently looked at a workaround for that character in particular though I don't recall whether it is in any released code!
{Mudlet stores your profile data scripts/aliases etc. in a (zipped?) XML format.}
Belgarath wrote:Highlighting text and right clicking for a copy is... Too fast. It disappears instantly before you can click on anything. This is on OSX Yosemite.
I applaud all the effort that has and is being put into this new release of mudlet. I know that incremental progress is being made.
Are there known problems with 3.0 that cannot be solved by our mudlet team in isolation? That require changes in third party software that mudlet is using? If so, is there a list of these resolve-required-by-third-party problems?
I'm having the same problem as https://bugs.launchpad.net/mudlet/+bug/1413435 in OSX. I've been using Delta for the last few weeks and apart from having to maximise/resize it when I open different profiles, that one mapper bug, and Mudlet crashing when I click on the search bar to look up something in the backlog, it is working very smoothly and efficiently.
Will there be a function for ANSI 256 colour support? I know that previous version of mudlet had support for 16 colours, in ANSI, but the getColorWildcard() function just returns false if I go higher.