|
Nomad Newbie
Joined: 11 Aug 2002 Posts: 6
|
Posted: Sat Sep 14, 2002 10:51 pm
Coloring more than one line of text |
I am tring to color more than one line of Text send to me by using a trigger with the #co 12 command
There is a lot of times it is longer than one line and it does not color more than one line.
I was wondering if any one had a way around this??
Any help would be nice :}
Nomad |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Sat Sep 14, 2002 11:05 pm |
quote:
I am tring to color more than one line of Text send to me by using a trigger with the #co 12 command
There is a lot of times it is longer than one line and it does not color more than one line.
I was wondering if any one had a way around this??
Any help would be nice :}
Nomad
Pretty sure that mud-side linebreaks (such as those for multi-line tells and such) stop any coloring command/function. Are you already able to capture the extra lines? If so, simply insert a color command in that/those triggers too.
EDIT: if it's ZMud doing the wrapping, then all the color commands should work normally
li'l shmoe of Dragon's Gate MUD |
|
|
|
Nomad Newbie
Joined: 11 Aug 2002 Posts: 6
|
Posted: Sat Sep 14, 2002 11:10 pm |
Well when i do a #cap on it . it only caputers one line also i have to do a #cap 2 to get the 2 lines
Nomad |
|
|
|
TonDiening GURU
Joined: 26 Jul 2001 Posts: 1958 Location: Canada
|
Posted: Sun Sep 15, 2002 12:53 am |
Post mud output of what you are seeing and tell us what you want captured.
Hard to guess not seeing what exactly you are doing.
Ton Diening |
|
|
|
Nomad Newbie
Joined: 11 Aug 2002 Posts: 6
|
Posted: Sun Sep 15, 2002 1:27 am |
Ok here is my trigger as it stands right now
#trigger {^Your comm unit relays a message from %w, "} {#co 14}
So the proplem is that it is set to trigger whenit sees that and the rest of it can be more than a one line response.
Like.. Your comm unit relays a message from Archangel, "We have been playing around with the defibrillators 0:-)"
and the defibrillators 0:-)" is on a second line and does not get any color
so thats whats up
Nomad |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Sun Sep 15, 2002 5:46 am |
First thing it try finding out if your mud allows you to set your screen width. If you can set it to as high a value as possible and then zMud will do the coloring correctly and take care of word wrapping. Currently you mud is doing the word wrap hence a hard line break and the second line does not fire any trigger. If you can't change the screen width then we can write a more complex trigger to color the second, third, forth... lines.
|
|
|
|
TonDiening GURU
Joined: 26 Jul 2001 Posts: 1958 Location: Canada
|
Posted: Sun Sep 15, 2002 5:48 am |
If you can't change your screen width and let zMud wrap for you (making it easy just to trigger it all and #COLOR it), this problem is similar to Rainchild's TellWindow (TM)
Probably a simple kludged way to handle finding where the " ends. Handling " tends to be messy.
#TRIGGER CommUnitRelayColoring {^(*)$} {#CO 14}
#T- CommUnitRelayColoring
#TRIGGER {^Your comm unit relays a message} {#CO 14;#T+ CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*"$} {#T- CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*"$} {#T- CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*$%*"$} {#T- CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*$%*$%*"$} {#T- CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*$%*$%*$%*"$} {#T- CommUnitRelayColoring}
#TRIGGER {^Your comm unit relays a message from %w, "%*$%*$%*$%*$%*"$} {#T- CommUnitRelayColoring}
Works based on the order of the triggers. Depending on where you get the "'s it could color more than you want.
Maybe someone can think of a cleaner way.
Ton Diening |
|
|
|
|
|