Colors

[Z-Man]

Which update would that be? I see no such thing happening, and no code change that could trigger it, not on 0.4 or trunk anyway.

[Light]

Here's a picture of what I'm talking about. It happened while I was on Linux, and still after I changed over to Win7. It was within the past 2 updates I believe, not counting the very last one from like two days ago. It happens in both fullscreen and windowed.

[Z-Man]

Maybe it does that for incorrect color codes now. I'll check.

[Jip]

Oh, this is the same I described in this bug though I forgot about it since I mostly use 0.2.8.

[Z-Man]

Doesn't happen to me, but I notice the first color code in that line of yours is missing the 0 in the beginning, that's a console bug we're chasing, too. So if you could produce a recording, that could maybe squash two bugs for the price of one!

[Light]

// Facepalm

[Z-Man]

Ops, sorry, whenever I say recording, I mean Debug Recording. I usually point that out, too, but you seem like a veteran who knows all that stuff already, so I forgot Videos don't help find bugs all too well.

[Light]

Ops, sorry, whenever I say recording, I mean Debug Recording. I usually point that out, too, but you seem like a veteran who knows all that stuff already, so I forgot Videos don't help find bugs all too well.

I was wondering why you wanted a recording, but I didn't even think of debug. I fail sometimes.

How do you do it in Windows? I tried running debug in codeblocks, but it didn't really show anything helpful. I built and ran, then joined the server, and after it started running, it logged nothing else except when I closed it.

Code: Select all

Building to ensure sources are up-to-date
Build succeeded
Selecting target: 
Win32 Release
Adding source dir: C:\Users\Light\Desktop\Armagetron\bzr_utd\win32\code_blocks\
Adding source dir: C:\Users\Light\Desktop\Armagetron\
Changing directory to: ../../build/dist
Adding file: ..\..\build\dist\ArmagetronAd.exe
Starting debugger: 
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
(no debugging symbols found)
Debugger name and version: GNU gdb 6.8
Child process PID: 3944
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program exited normally.
Debugger finished with status 0

[Light]

blah ignore that question - i see how sry (not much of a windows person)

[Light]

http://www.mediafire.com/?phrqdxaxajb02bj

Sorry for my stupidity lol. I'm not with it today.

[Z-Man]

Ah, interesting. It affects the Windows build only, no wonder I couldn't reproduce it. Thanks, the recording helps a lot.

[Light]

Ah, interesting. It affects the Windows build only, no wonder I couldn't reproduce it. Thanks, the recording helps a lot.

That's weird because I'm pretty sure it happened on the Linux build too. I will be installing Linux again soon, so I can see for sure then.

[Z-Man]

It actually depends on whether FTGL and freetype support utf8. Both bugs were fixed once I implemented a TODO for the case that they don't. I'll try updating the libraries in winlibs ASAP as all that utf8 to wchar translation is costy.