Zugg Software :: View topic

Beginner Joined: 12 May 2003 Posts: 24

Ok, I have the main window...and I use a trigger like this

#trigger {@names} {#cw 10}

with the variable "names" containing a list of names to highlight. Now, this works wonderfully for the main window, but when I want to have those names highlighted in the child windows...it never works right. It is probably because I want to format my output to the other windows...using something similar to this...

#TRIGGER {Your mind hears (%w) thinking, &%*{Thought}} {
#GAG
#WINDOW {Thoughts} {%concat( %ansi( high, yellow), %time( " [hh:nn:ss]"), %ansi( high, red), "[%1] ", %ansi( high, green), %expand( @Thought, 1))}
}
Is there any way to output "modified" text to a child window, but still have the highlights work correctly?

Enchanter Joined: 10 Oct 2000 Posts: 698

quote:

Ok, I have the main window...and I use a trigger like this

#trigger {@names} {#cw 10}

with the variable "names" containing a list of names to highlight. Now, this works wonderfully for the main window, but when I want to have those names highlighted in the child windows...it never works right. It is probably because I want to format my output to the other windows...using something similar to this...

#TRIGGER {Your mind hears (%w) thinking, &%*{Thought}} {
#GAG
#WINDOW {Thoughts} {%concat( %ansi( high, yellow), %time( " [hh:nn:ss]"), %ansi( high, red), "[%1] ", %ansi( high, green), %expand( @Thought, 1))}
}
Is there any way to output "modified" text to a child window, but still have the highlights work correctly?

It is redundant, but you could try duplicating your #trigger {@names} {#cw 10} in the child window.

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

Triggers (and other settings) belong to a particular window. To use #CW in two windows, you'll have to create a #CW trigger in both windows. You'll also need to create the variable in both windows.

LightBulb
Advanced Member

Beginner Joined: 12 May 2003 Posts: 24

ok, how do I put the trigger in the window? and for the record, if I used one of the other commands to send names to the child window, it did highlight in the child window without the need of a separate trigger. I just lost half of the information, so didn't do it that way.

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

There are three ways I can think of to put a trigger or other setting in a child window.
1. Switch to the child window and use the Settings Editor
Triggers button
2. Switch to the child window and use the command line
#TR
3. Send the command to the child window using the focus character
:Thoughts:#TR

#CAPTURE will capture the line as is, and display it in the child window. This includes any #CW (or similar) commands that have already been processed. It does not include any #CW commands which have not been processed at the time of the #CAP trigger. Therefore, the actual display in the child window, if it doesn't have its own set of #CW triggers, would depend on the order of triggers in the main window. But since you find #CAP unacceptable anyway, I don't know why you'd make an issue of it. It won't lose any information, but it also won't add any or reformat a line.

LightBulb
Advanced Member