Zugg Software :: View topic

Newbie Joined: 05 Aug 2004 Posts: 3

On Gemstone, I'm capturing logins and logoffs to another window, but everytime it captures, it's still producing a newline on the main window.

#TR {$%1 %2 joins the adventure.} {#gag;#cap Logging}

Any suggestions?

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

Suggestion 1. Don't use numbered parameters (%1 - %99) in trigger patterns. They are intended for trigger values (where the commands go) and aliases. Use * in patterns, it has the advantage of being documented as a pattern wildcard.

Suggestion 2. Don't use multiline trigger patterns (ones that have $ anywhere except the end) with commands which act on an entire line, such as #GAG and #CAPTURE.

Suggestion 3. If you want to remove the previous line, use #GAG -1.
#TR {joins the adventure.} {#GAG;#CAP Logging;#GAG -1}

Newbie Joined: 05 Aug 2004 Posts: 3

Well, I changed the parameter to %w
Removed the multiline trigger patterns
And added the #gag -1.

I'm still getting blank lines on my main window.
I removed the #gag -1, and it made no difference.

Newbie Joined: 05 Aug 2004 Posts: 3

(Edited by author)

After lots of searching here, I found the problem. :>

Thanks Zuggy

Beginner Joined: 14 Sep 2004 Posts: 17

I'm having a similar problem. When using gag -1, it's still scrolling the screen with a blank line. When using gag -2, it doesn't scroll the screen, but I find it is gagging text other than what I have it triggered to gag. For example, sometimes it will gag a shout, or somebody walking into my room, when I only want it to gag a yell. In addition, using gag -2 makes it almost impossible to read anything on your screen because it causes the screen to move up and down for a brief second when it gags the necessary text. What would be ideal, and what I'm trying to figure out is, if it's possible to gag the text from the screen, keep it from scrolling an extra line when the text is gagged, and keep the screen from "bouncing" when it does gag the text. Any help would be appreciated.

Magician Joined: 23 Apr 2003 Posts: 358 Location: USA

Use #GAG without any parameters to gag just the line triggering. #GAG -x gags the next x lines.

It would help use center on your problem is you show us what the unwanted text looks like (in context with other lines), and what trigger you're using that isn't working as desired.

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

Add a #COND to your trigger to match and #GAG the next blank line.

#TR {joins the adventure.} {#GAG; #CAP Logging}
#COND {^$} {#GAG}

Beginner Joined: 14 Sep 2004 Posts: 17

Using a #cond trigger still isn't fixing the problem. My trigger looks like this:

#trigger {~[~(MM~)~]} {#gag;#cap logging}

Whenever that string shows up, it does capture it properly, but it still scrolls my screen one line. When I gag this line, I don't want my screen to scroll, I want it to look like it never appeared at all, and just have it logged to the other window.
Is there any way to do this?

I tried using this:

#trigger {~[~(MM~)~]} {#gag;#cap logging;#gag -1}

but it still scrolls the screen a line. I tried using this:

#trigger {~[~(MM~)~]} {#gag;#cap logging;#gag -2}

and this seems to work, except it seems to #gag lines I don't want gagged sometimes, and it also "jolts" the screen sometimes when the required text is gagged, causing it to be very difficult to read long descriptions.

Enchanter Joined: 10 Oct 2000 Posts: 698

KurtDH - Try checking/unchecking the line EOR/GA in preferences.. I think that's what it is, I don't have zmud open to check atm.

Beginner Joined: 14 Sep 2004 Posts: 17

It was checked. I tried unchecking it and trying everything I tried above, and it didn't fix the problem.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

For some reason your trigger looks like a prompt item. If it actually is and it is set to fire on prompt instead of newline then what happens is the prompt is received, the trigger fires and gags it, then when the newline is received you end up with a blank line. Assuming this is your situation make a seperate trigger for the gagging that will fire on newline.

Beginner Joined: 14 Sep 2004 Posts: 17

SubAdmin Joined: 18 Nov 2001 Posts: 5182

By "prompt item" I meant something you would see in your prompt line. Since this doesn't seem to be the case I am out of guesses. Why don't you post a copy of the text from your mud with the trigger turned off. Then post a copy with it on, and finally post the entire trigger. Guessing just isn't fun.

Beginner Joined: 14 Sep 2004 Posts: 17

I don't think posting text from the MUD will help. The problem I'm having is with scrolling, and that can't be construed with a capture from the MUD. I figured this would be a relatively easy question to answer because I thought the whole point of the GAG command was to get rid of unwanted text and unwanted scrolling. By using just #gag with no parameters, it gets rid of the text, but the unwanted scrolling is still present. Using #gag -2 gets rid of the text AND the scrolling, but it causes the screen to "bounce" for a brief second when the required text is gagged. I wouldn't have a problem with using this method except for two reasons. First, the "bouncing" effect makes it very difficult to read any long descriptions because you have to constantly find where you left off after the screen is finished "bouncing." Second, using #gag -2 sometimes gags text that I don't want gagged in the first place. For example, I'll see a string of text on my screen such as a shout, and then when the required text shows up and it is gagged, the shout text disappears from my screen. This is telling me that the trigger is also gagging lines I don't want it to gag. Does nobody know what I mean when I say the screen "bounces"? The screen is actually scrolling for a brief millisecond, but then the #gag -2 brings the screen immediately back to its original position, making it seem as if the screen is bouncing. I want to eliminate this, is it not possible?

Beginner Joined: 14 Sep 2004 Posts: 17

Grelf, I'd appreciate it if we could get your input on how you ended up fixing your problem. You're having the same exact problem I'm having.

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