|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Sat Feb 06, 2010 3:14 pm
[3.14] ANSI issue |
My Ansi code below suddenly stopped working correctly for some unexplained reason this version. The first '[' should be coloring properly, but isn't:
Code: |
#say %ansi( blue)~[%ansi( red)NPC%ansi( blue)~] |
|
|
|
|
shalimar GURU
Joined: 04 Aug 2002 Posts: 4691 Location: Pensacola, FL, USA
|
Posted: Sat Feb 06, 2010 4:21 pm |
confirmed
|
|
_________________ Discord: Shalimarwildcat |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Feb 06, 2010 6:05 pm |
Damn. Yet more ANSI bugs. I swear, the ANSI/MXP emulation is one of the areas of CMUD that I just hate working on. Everything is so intertwined that when I fix a bug in one place, it causes a side effect somewhere else.
In this case, the problem is that the #SAY command is first trying to switch to the "information" Style. And the %ansi(blue) isn't overriding that style for the first character.
If you change your command from #SAY to #SHOW (which doesn't use any specific style), then it works.
Added to the bug list. |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Wed Mar 31, 2010 3:49 am |
How many versions are going to go by before this bug introduced in 3.14 is addressed?
|
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Wed Mar 31, 2010 5:21 am |
It's a very minor one, wherein the ansi doesn't work but the MXP does. Is there any particular reason you don't want to use MXP?
|
|
_________________ EDIT: I didn't like my old signature |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Wed Mar 31, 2010 5:34 am |
My scripts were all written pre-bug and worked perfectly then. Why should I have to go back and redo a bunch of my code to code around a newly introduced bug?
|
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Wed Mar 31, 2010 5:36 am |
If having this functionality is antiquated and shouldn't be used then officially deprecate it and forbid it's usage, don't just allow it to continue buggy, that's just bad form.
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Mar 31, 2010 3:59 pm |
Quote: |
How many versions are going to go by before this bug introduced in 3.14 is addressed? |
Well, let's see, since 3.16 is the first Beta version available to general users since 3.14, I'd say just more than one. You should know by now that I do not fix *every* bug in every new release. I have 134 bugs on my "sometime in the future" bug list. This is considered a minor bug because it only happens with the #SAY command with very specific ANSI color codes. And it's only a visual bug unless you are using an ANSI trigger, which means it effects even fewer users. Given the small number of people using the Beta version, you are probably the only one who cares about this one.
You don't need to rewrite your scripts. No functionality is being antiquated. But I have a lot of more important bugs on my list before I get to this one, sorry. |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Thu Apr 01, 2010 2:13 pm |
That syntax wasn't originally my own. Larkin was the creator of that syntax when he created his popular Acropolis curing system for Achaea. Any people still using that system are likely to be hit by this as well.
|
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Wed May 12, 2010 2:10 pm |
Confirmed fixed in 3.17.
|
|
|
|
|
|