 |
robert
Wanderer
Joined: 25 Feb 2004
Posts: 98
|
 Posted: Mon Nov 26, 2007 5:21 am
[2.13 Pro] Capturing text that goes from ANSI to null ansi results in black text
|
Unforuntately I don't know how an average user can reproduce this. However the line of text I receive is something like this with ansi codes:
| Code: |
<ESC>[37;1mChat [Tester]:<ESC>[0m Testing! Testing!<CR><LF>
|
When I receive this, everything seems fine on the original window. If I do a #CAP on that to a different window, the "Testing! Testing!" will be the same color as the background color such that it isn't visable unless highlighted. This did not occur in 2.11 but does now in 2.13. I didn't find a CMud command that would display out a raw ansi input and parse it as it if came from the mud to be able to reproduce this without some type of server.
Thanks! |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Nov 26, 2007 5:11 pm
|
I am not able to reproduce this. I need you to capture the text from the MUD that shows this bug. In CMUD, type the following command:
#DEBUGFILE test.raw test.txt
and then do whatever on the MUD to cause the problem text to be displayed. Then exit CMUD and email the test.raw and test.txt files to sales@zuggsoft.com so that I can replay them here to see the bug. |
|
|
|
|
robert
Wanderer
Joined: 25 Feb 2004
Posts: 98
|
Posted: Tue Nov 27, 2007 2:17 pm
|
When I tried "#DEBUGFILE test.raw test.txt" I got a parsing error for unknown command #DEBUGFILE. Also fyi I have changed the foreground color of both my main session window and my capture session window to silver. However if I change the foreground to other colors, the issue is still there.
Thanks! |
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Tue Nov 27, 2007 6:05 pm
|
When you installed 2.13 was it an upgrade install or a clean install? Are you running Vista. There was another instance where someone could not access the commands and it seems there was an old version of their cmd.db floating around on their file system. You can check the date of the of your cmd.db and search your PC to see if you have more than one copy.
|
|
_________________
Asati di tempari! |
 |
|
|
robert
Wanderer
Joined: 25 Feb 2004
Posts: 98
|
Posted: Tue Nov 27, 2007 7:21 pm
|
It was a dreaded upgrade install. ;) I will try deleting the Program File/CMud directory and see if that resolves the issue. I am running Vista Home Premium 64-bit.
|
|
|
|
|
Arde
Enchanter
Joined: 09 Sep 2007
Posts: 605
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Nov 27, 2007 9:07 pm
|
Make sure when using Vista that when you install CMUD you select the DEFAULT locations for the Program files and Data files. Do *not* store your data files in the same directory as the program files. This causes Vista to create a shadow copy of various files and will cause nightmares during upgrades. I'm going to try and make the installer smarter so that this option for Datafiles isn't even available on Vista.
|
|
|
|
|
robert
Wanderer
Joined: 25 Feb 2004
Posts: 98
|
Posted: Wed Nov 28, 2007 12:41 am
|
Ok, I deleted my CMud directory, and I deleted the virtual store for CMud. Just deleting the CMud directory fixed my #DEBUGFILE issue. However the ANSI issue is still there. I have e-mailed you the test.txt and test.raw.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Nov 28, 2007 5:04 am
|
I received the files and was able to confirm the problem with the capture window.
|
|
|
|
|
|
|
|
