Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

So, I logged in color, opened it in the editor as a color log. Firstly, I don't like that it has the minimize button but doesn't minimize, a minimize feature would be really useful. However, that is not my problem. Being a long log, I didn't have time to finish cleaning it up so I decided I would save it as an ansi log file. I opened it up and...

As you can see, my prompt suddenly has a gray background. Not to mention all of the editing work I had done before is gone, I was trying to go through and put line breaks to add some spacing between many of the lines. I don't know why it did this or what I should be saving it as should I wish to preserve my work before going html.

Posted: Fri Jun 06, 2008 2:28 am

If you can send me the log file as an email attachment and then give me the instructions for reproducing the problem, then I can try it here.

I'll add the problem with not minimizing the editor window to the bug list. It used to work, so I'm not sure what changed recently to cause that.

Posted: Mon Jun 09, 2008 8:33 pm

OK, I see several problems here. First, yes, it's true that the Editor window isn't handling ANSI colors the same as the main MUD window. The problem here is that the Editor window is using a "Rich Text" control to allow editing of colored text and HTML. Where-as the MUD window is using a custom display component that I wrote which can handle ANSI, MXP, MCCP, and all of the other MUD protocols.

While the Editor window has some ANSI color capabilities, it doesn't have some of the features of the main MUD window. For example, in the ANSI standard, using ESC[1m turns on "bold font". In CMUD, the "bold font" flag can be used to select a "bright color" for the text. Actually, in the ANSI Preferences page, you can completely customize what CMUD does in response to the "bold" code (and other ANSI codes).

But the Editor is just doing "standard ANSI", so instead of bright colors, you get a bold font, which is what the ANSI standard originally intended. Since the Editor is using a 3rd-party Rich-Text editor component, I don't have a lot of control over it.

In zMUD, the Editor used the same component as the MUD window. But this custom component had all sorts of weird troubles being used as an editor (it was designed and optimized for scrolling incoming text, not for editing that text). By using a 3rd-party editor component, I was able to remove all of the editor bugs that MUD had, and was able to add stuff like support for editing HTML files. But at the cost of less ANSI compatibility.

Anyway, I've put this on the to-do list for the future to see if I can improve how the ANSI support in the Editor is handled.

Wizard Joined: 26 Mar 2008 Posts: 1547

Thank you