Zugg Software :: View topic

Posted: Mon May 30, 2011 10:08 pm

After using #SAYADD to concatenate several lines from the game together... is there away i can have the new superline retested as if it was just sent from the mud?

Posted: Mon Jun 20, 2011 2:18 pm

Posted: Mon Jun 20, 2011 2:33 pm

I was thinking lines that #sayadd had been used on were retested. I made two triggers to give it a test and the second trigger fires off the new line #sayadd was used on.

Posted: Mon Jun 20, 2011 2:48 pm

I have an OOC window, inside of which i made a simple test trigger:

#TR {^test} {#CO red}

Then i entered the following on the command line:

#WIN OOC {test}

which works fine... then i tried the following command:

:OOC:#SAYADD { hi}

Firstoff... for some reason the sayadd is going to a seperate line instead of appending...
then if i do the #WIN again... it appends instead of starting a new line

So I try the following:

#EXECWIN OOC {#say {test};#WAIT 2000;#SAYADD { hi}}

and the same can be seen

If i put the #SAYADD into the trigger it appends properly

The same commands and trigger in the main window work fine, but as you can see, #SAYADDing does not cause the trigger to refire

Sorcerer Joined: 15 Apr 2011 Posts: 809

Hmm, this looks like a bug to me. #sayadd is tacking on a carriage return before your entered text, instead of after. Not only is the #sayadd going to a separate line instead of appending (which really kinda defeats the purpose... Razz

) the next line in that window is going onto the same line as the #sayadd-ed line. Using your example:

Posted: Wed Jun 22, 2011 4:12 pm

It's not #sayadd that is the problem. The problem is you are using the #window command to send the initial text and #sayadd is designed to follow a #say command. For example, this works fine:

Posted: Wed Jun 22, 2011 4:18 pm

My original question was weather i could force the new superline to be retested.
That it doesn't currently I already know.
Maybe let #SAYADD have a second boolean parameter?

Also... why the limitation on what #SAYADD can follow?
it follows regular mud text and #CAPTURE just fine, that it doesnt work following #WIN seems like a bug.
and it doesnt explain why the #EXECWIN fails

Posted: Wed Jun 22, 2011 4:50 pm

All of these issues have come to light from my trying to kludge the #CAPADD command i had suggested.

Apprentice Joined: 22 Mar 2009 Posts: 149

You might be able to rig something together by storing the lines you want to have concatenated together in to a variable, then sending them to the child window all at once rather than capturing them piecemeal. By sending the concatenated lines to the child window with a single #SHOW command, rather than a combination of #CAP and #SAYADD they'll be tested by triggers the way you desire.

Posted: Thu Jun 23, 2011 9:28 am

The above example was contrived, to explain what i was talking about.
And to illustrate abnormal behavior (which doesn't seem to be getting recognized as such by Zugg).

What i truly want is:
1. a means to retain mud color (ala #CAPTURE)
2. while appending it to the end of a line in another window (ala #SAYADD),
3. preferably while also %trim ing away all but a single character of whitespace

(3 could be done by using a #SUB command prior to my suggested #CAPADD command, linked to in my post prior to this one)