|
titanium Beginner
Joined: 13 Oct 2001 Posts: 18 Location: USA
|
Posted: Mon Dec 30, 2002 8:45 pm
#Capture |
How can I use #CAPTURE and when it captures a tell it will put it in a window, but it will only show up in that window and not the main one?
(%W) tells you, 'hi'
Titanium |
|
|
|
doomfyre Apprentice
Joined: 03 Jan 2002 Posts: 152 Location: USA
|
Posted: Mon Dec 30, 2002 9:24 pm |
#TRIGGER {^(%w) tells you, '*'} {#CAP Tells; #GAG}
Depending on how your mud is set up, this may not capture multiple lines, and could also leave a blank space on your main window. |
|
|
|
titanium Beginner
Joined: 13 Oct 2001 Posts: 18 Location: USA
|
Posted: Mon Dec 30, 2002 9:31 pm |
Anyway to make it so the blank lines won't show up? Oh and is there a way to put it all in one window...chats,tells, shouts,etc...
Thanks |
|
|
|
Death Apprentice
Joined: 25 Jun 2002 Posts: 109 Location: USA
|
Posted: Tue Dec 31, 2002 7:17 pm |
Yea, just make triggers for every kind, or you could make one and use variables and probably shorten it down alot. I've got a question about #capture. Which is better? #win or #cap, right now i'm using #win to get the global messages and chats to a seperate window, but I want to end up setting up an automatic logging of that other window with the date and time of when it started as the name(when I logged on.)
Thanks,
Death |
|
|
|
AzCowboy Adept
Joined: 09 Nov 2000 Posts: 222 Location: USA
|
Posted: Tue Dec 31, 2002 7:37 pm |
Neither one is 'better'... they perform different functions, so which you use depends on what you want to do.
#CAP captures the line verbatim to the designated window,
#WIN sends whatever text you tell it to to the designated window, so you could easily add a timestamp right into the #WIN command to timestamp each line as you send it. |
|
|
|
Death Apprentice
Joined: 25 Jun 2002 Posts: 109 Location: USA
|
Posted: Tue Dec 31, 2002 7:47 pm |
Well, I've got a %time function on some of the triggers to send it there, like log ons, log offs, disconnects, reconnects, etc... But is there a way to have it set up a log file with the file name the date and time into a designated folder inside the zmud directory, with or without color (if there's a way to get the color of it to a log file or website, that'd be cool...I read about some ansi to html converters and looked in the history of the forum, but all the links to the programs/plugins aren't working.
-Death |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Tue Dec 31, 2002 8:03 pm |
#AL atconnect {#LOG %time(ddmmmyy).txt;#SAY Connected at %time()}
That gives you the date as your filename, with both the time and date at the beginning of each connection. Multiple connections on the same day will be appended to the existing file with another time stamp. Logging color codes (and other logging options) is controlled by Preferences, on the General/Logging screen.
LightBulb
Senior Member |
|
|
|
Death Apprentice
Joined: 25 Jun 2002 Posts: 109 Location: USA
|
Posted: Tue Dec 31, 2002 10:18 pm |
Anyway I can have it send the logs to a designated folder?
-Death |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Dec 31, 2002 10:26 pm |
Include the whole path in the #LOG command instead of just the name of the file.
Kjata |
|
|
|
Death Apprentice
Joined: 25 Jun 2002 Posts: 109 Location: USA
|
Posted: Wed Jan 01, 2003 5:31 pm |
It works when I do it manually, I have to do it manually because it won't save the trigger in the secondary window after I shut down zmud. So when I boot it back up the next time, the trigger is gone and the logging won't begin. I've tried saving it as something, but it still doesn't seem to want to load up next time zmud is started. Anything i'm doing wrong?
-Death |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Wed Jan 01, 2003 6:29 pm |
Save the settings of the other window. Be sure that the settings file has the same name as the window.
Kjata |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Wed Jan 01, 2003 7:17 pm |
Just modify your atconnect alias to send the commands to the desired window.
#AL atconnect {:windowname:#LOG {path~%time(ddmmmyy).txt};:windowname:#SAY Connected at %time()}
LightBulb
Senior Member |
|
|
|
|
|