 |
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
 Posted: Sat Mar 27, 2010 5:32 am
[3.16]BUG: #PSUB issues with new syntax
|
It seems that #PSUB {text} 0 -1 is having some issues working correctly. If you have two triggers with #PSUB on it, and they fire on the same line, #PSUB messes up. Here are the steps so you can see for yourself.
Steps:
1. Open untitled session.
2. On command line, type #TRIGGER {test message.} {#PSUB {Message fired!} 0 -1}
3. Confirm it works by typing #SAY {This is a test message.} on the command line.
4. On command line, type #TRIGGER {(This)} {#PSUB {} %x1}
5. Repeat the command in step 3.
You'll notice that the message fires, and both #PSUBs NEARLY work, except it's keeping the 'T' from 'This' in with the message, so instead of:
| Quote: |
| Message fired!is a test message. |
you get:
| Quote: |
| Message fired!tis a test message. |
Incidentally, and this might be cause for another bug report, but it deals with #PSUB, #PSUB seems to strip the first color with the following steps:
1. Create a trigger such as #TRIGGER {(Psub)} {#PSUB {} %x1}
2. On command line, type #SAY {Psub%ansi(red)%ansi(white)bing is a great way to retain color!}
You'll see that the opening ( is white instead of red. It seems that if it changes color after the first character, it won't work properly. Not sure what's going on with it, though.
Charneus |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sat Mar 27, 2010 7:03 am
|
#PSUB (and #SUB) both strip ansi color codes associated with the matching text. That has been a known problem for a long time. It's on the bug list, but there isn't an easy fix, so it has been a low priority.
Reproduced the first issue and added it to the bug list. |
|
|
|
|
|
|
|
|
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
|
|
