 |
Progonoi
Magician
Joined: 28 Jan 2007
Posts: 430
|
 Posted: Mon May 12, 2008 9:18 pm
Bug with ansi triggers with additional conditions?
|
I know that ZMud is feature complete and also bug-fix complete and I don't come across one to even bring it up but
I think now I did.
| Code: |
#CLASS {ansi}
#VAR line {}
#TRIGGER {%e[32m(*)%e[0m$} {#say Green Text.} "" {color}
#COND {(*)$} {#say Line following it within 1.;line=%1} {within|param=1}
#CLASS 0
|
Very randomly the {color} bit disappears and I have to re-check it under trigger options. While I was writing the cond and switched back to trigger's first stage and checked the options, I saw the ansi being unchecked, too.
I haven't messed around with ansi triggers before so thats first time I came across it and maybe there's some simple workaround I can use or I'm just doing something wrong.
EDIT: Notice the %e[0m. Before someone says that the culprit I doubt it. I had to use it because otherwise I got weird half text-half ansi color codes data into a variable where I captured the data the green text contained.
Also, when I go back and edit the condition, finish doing it and go back to first state, then go the options of the first state, I can see ansi being unchecked yet again.
Thanks for help in advance,
Prog |
|
|
|
|
Progonoi
Magician
Joined: 28 Jan 2007
Posts: 430
|
Posted: Tue May 13, 2008 2:41 pm
|
Bumping it because almost half hundred views and no suggestions yet... :/
Prog |
|
_________________
The Proud new owner of CMud.
--------------------------------
Intel Core i5-650 3,2GHz
4 DD3 RAM
GTX 460 768MB
Win 7 Home Premium 64x
-------------------------------- |
 |
|
|
|
|
|
|
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
|
|
