Zugg Software :: View topic

Newbie Joined: 06 Nov 2006 Posts: 6

created trigger:
Pattern: %w {tells|tell|rtells|rtell} %w '*'$
Script: #CAP 1 Tells

in a common package where I hold triggers etc. that are common to all my characters.

Problem:
A 'Tells' window was created, and the triggering line (So-and-so tells you 'sup') was copied to it... several times over. A little window popped up telling me an endless loop had been detected, and asked me if I could like to disable the trigger.

I assume the problem is that the trigger is firing for the Tells window as well. I would assume that #capture should recognize this... I realize it can be worked around, but one shoudn't have to fix lots of windows just to use #capture. It should work by default.

Posted: Fri Dec 29, 2006 1:30 am

The proper way to do it is quite simple. Put the Tells window and the module containing the trigger into the same package. Set the module to External Only. Job jobbed :)

Newbie Joined: 06 Nov 2006 Posts: 6

Yeah, but my point is that capture (and all functions) shouldn't have to be "worked around" unless you're doing something funky with them. capture's job is to capture to another window, it should work without work-arounds.

Posted: Fri Dec 29, 2006 1:50 am

Gauther that is not a work-around it is the prescribed i.e. Zugg branded way to do this.

With the introduction of packages, scoping and other concerns (which were discussed at length in the BETA forums), it was decided through consensus of Zugg and the Beta developers that this is how it should be handled.

I don't have the link handy, but I'm sure if you search for it you'll find it.

Newbie Joined: 06 Nov 2006 Posts: 6

Oh, k. Nevermind then. I'll find some other way to do what I want :)

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

The 'normal way' can be demonstrated easily though by just opening CMUD, going to a new untitled session and creating the trigger, then testing it. It works fine in a new session.