|
Daern Sorcerer
Joined: 15 Apr 2011 Posts: 809
|
Posted: Wed Jul 04, 2012 4:26 pm
(Bug?) Color syntax and local echoes |
Copying locally echoed text (from the #say, #echo and #print commands) does not correctly add color codes as defined in color syntax. It does copy @F (the general syntax for foreground color - NOT a real color code) when text is echoed in the default color (cyan), but nothing when text is echoed in other colors, set with %ansi. Interestingly, color codes are added perfectly when using #show. Is this a bug?
EDIT: They don't copy right when using #window either. I just get @F's whenever there's a color change. I've posted that one before, but didn't get any answers. |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Wed Jul 04, 2012 5:29 pm |
The bug appears to be in %ansi(), and perhaps in any of the other clientside coloring functionality we have (didn't start on #CW/#COLOR/#PCOL/mxp yet). When you use the 16-color numerical values for the colors, the colorsyntax substitution works fine in all cases EXCEPT at the beginning of the selection. In that case, you either get @F or no colorsyntax code at all. The only thing I wonder about is that the color representation in %ansi() seems to be backwards (ie, 1 = bright blue, 2 = bright green, etc). This might've been a recent design change, though, since the dim versions are generally harder to read.
Gameside color replacement works perfectly fine, though, and I think the reason #SHOW is also showing no problems is because it's pretending to be something sent from the game. |
|
_________________ EDIT: I didn't like my old signature |
|
|
|
hadar Apprentice
Joined: 30 Aug 2009 Posts: 198 Location: my apt, in california
|
Posted: Wed Jul 04, 2012 5:55 pm |
it always works right for me, only time i ever get that problem is when im trying to copy xterm colors
Could it be something askew with your settings? |
|
|
|
Daern Sorcerer
Joined: 15 Apr 2011 Posts: 809
|
Posted: Thu Jul 05, 2012 2:31 am |
Interesting... I hadn't thought to test using the numerical values with %ansi, my testing was just done with color names (e.g. "#say %ansi(green)test") and I was getting no color codes. So it looks like there's two bugs here, possibly related: 1) The default color copies as @F, the general syntax for changing foreground color, and 2) %ansi with color names in words produce no color codes. I've got my workaround for the moment anyway, it'll be annoying to have to change dozens of names to numbers, but at least it works.
|
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|