Reload-Logs & Line-Colors - Ctrl+O - Bug - 22/03/06 12:01 PM
Hi,
I've noticed a small bug using the "Reload Logs" and the "Line Colors" functionality:
When both of the above settings are activated and a line that had a color specified and contained a color-reset-character (Ctrl+O), the color will not be reset to the intended color, but the system default.
activate both settings and try the following:
If you have another default-text-color than 5 you will see, that after $chr(15) (which is Ctrl+O) the line is in another color. Personally I even noticed that a timetag got applied to the line when it was reloaded from the logs, whereas it does not get one when first 'echo'ed.
It's just a minor cosmetical fix, just noticed that odd behaviour.
Konfu
I've noticed a small bug using the "Reload Logs" and the "Line Colors" functionality:
When both of the above settings are activated and a line that had a color specified and contained a color-reset-character (Ctrl+O), the color will not be reset to the intended color, but the system default.
activate both settings and try the following:
Code:
/query test //echo 5 test this $chr(2) is $chr(22) just $chr(15) a $chr(31) test /close -m test /query test //echo 5 test this $chr(2) is $chr(22) just $chr(15) a $chr(31) test
If you have another default-text-color than 5 you will see, that after $chr(15) (which is Ctrl+O) the line is in another color. Personally I even noticed that a timetag got applied to the line when it was reloaded from the logs, whereas it does not get one when first 'echo'ed.
It's just a minor cosmetical fix, just noticed that odd behaviour.
Konfu