Zugg Software :: View topic - #CAPUTRE maintaining colors and line integrity

Wanderer Joined: 07 Oct 2001 Posts: 71

I've got a good and working capture trigger for multiple lines of text. However, the child window that the text is sent to is only 1/4 as wide. Everything works perfect, but I would like someway to send the received text to the child window without carriage returns. It's causing it to look very choppy in the child window, because each line captured is being seperately wordwrapped. The twist here, is I want to maintain the colors from the mud.

Oh, I have one other seperate small problem. One of the color triggers I have for peoples names uses "#CW blanchedalmond". Whenever someone whos name is in that trigger, uses one of the channels I capture, their name is sent to the child window black. It looks like a blank space where their name should be, however you can highlight the text and see the name is actually there, just black. Yet the names who I trigger with #CW Red are sent to child windows fine. Any thoughts?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

The color problem is a known bug with mxp colors (the ones listed under %colorname). Put a #CW trigger in the child window to change the color there. The standard colors and attributes aren't affected. They are black, blue, green, cyan, red, magenta, brown, gray, yellow, white, hi, bold, rev, blink, and under.

Carriage returns are sent from the MUD. There's no way to prevent #CAPTURE from including them. You can try to come up with a trigger in the child window to remove them, but you'll probably lose at least part of the color information.

Wizard Joined: 14 Oct 2000 Posts: 1368

Wanderer Joined: 07 Oct 2001 Posts: 71

IS there maybe a way store the line I wish to capture WITH the ansi codes included in a variable, so that I could use #SAYP or something like that to send it to the child window with the ansi codes to maintain color, without the carriage returns?

Wanderer Joined: 07 Oct 2001 Posts: 71

And as for the MXP color problem, could I possibly use the Priority tag to cause the line to be captured to the child window, before the MXP color tag is Substituted in?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

1. Yes, the bug is known. I personally reported it on the Beta forum in October of last year. If it's not in the database go ahesd and add it.

2. Anything might be possible, but I can't think of a way to do it.

3. The #PRIORITY command doesn't affect the order in which triggers are evaluated, it only prevents loops from being run in the background. However, it is possible to change the order of triggers so that the #CAPTURE trigger is first.

Open the settings editor with the Triggers button
On the settings editor View menu select Sort By ... None
On the settings editor View menu select All Classes
Select the #CAPTURE trigger
Use the arrow buttons to move it Up the list until it's above all the #CW triggers