Zugg Software :: View topic - [2.37] #Gag change causing an issue with an prompt event.

Posted: Wed Dec 31, 2008 6:25 am

Since the rework of how #gag works I've had two issues.

1) I have a prompt event that will not fire if the line before it is gagged before the event is enabled. It only works correctly if I enable the prompt before gagging the line before the prompt.

(Edited: See below for a better example)

2) When I #gag a line sometimes it reappears a few lines later as text is scrolling up the screen. So the sequence is the following:

a) The line is #gagged and I print something out in place of the gagged line.
b) A few lines go by and then the #gagged line reappears.
c) Another line is received and the newly reappeared (but previously gagged) line disappears again.

I have no idea what causes it. It doesn't happen all the time, but it does happen from time to time with a certain regularity.

Posted: Wed Dec 31, 2008 11:16 pm

I've mocked up a small example of the issue. In this example I have a regex that detects the prompt and fires a Prompt_test event. There are two receivers of this event, one that is enabled every line which prints out "(control)" to show that a Prompt_test event fired. The other one prints out "(enabled)" when it is enabled and receives the event. I execute a command that returns "There is no such person, I'm afraid." which executes some code which does a #show/#gag/#delitem and enables the "(enabled)" prompt printout. It should be printing out "(enabled)" on the very next line, but it doesn't. Only if I switch the order of the #show statement does it enable correctly.

Code for incorrect operation:

Posted: Wed Dec 31, 2008 11:40 pm

I whittled it down a bit more to the essentials. Looks like this is an issue with #show. When I change it to #say the issue goes away.

Posted: Thu Jan 01, 2009 1:25 am

This might also be interfering with the #DELITEM which sometimes doesn't delete the item from the array depending on the ordering of the section. I tried for hours to get something reproducible where #DELITEM wouldn't erase the item from the array depending on the ordering of the statements, but it was very elusive. Even when I had the ordering correct it would only sometimes work in my actual code and never in my mocked up example. But just in case something occurs to you regarding #DELITEM and the #SHOW bug shown here, I'll add this as another possible related issue.

Wanderer Joined: 06 Apr 2007 Posts: 59

Wow, I'll take a look at this after I have some coffee. Long night last night. ;)

Wanderer Joined: 06 Apr 2007 Posts: 59

Okay, from my own experiences with #SHOW, it displays text as though it was sent from the mud, so it's vulnerable to #GAG commands. I never really played with #SAY.

My own experiences with #GAGging trigger text has been successful and I've built an entire suite based off of that style of operation.

An acceptable alternative, perhaps, is #SUB your triggered message in place of the original trigger line. Or, place the #SHOW just after the #GAG command.

Posted: Thu Jan 01, 2009 8:11 pm

I've already coded around it. I'm posting it here so it can be fixed.

Posted: Tue Jan 06, 2009 6:11 pm

Has anyone been able to replicate this behavior? You'll need your own trigger that raises the 'Prompt' event and to edit the trigger "There is no such person, I'm afraid." to something similar on your Mud, but otherwise this should be able to be replicated.

Posted: Wed Jan 21, 2009 7:32 am

Delete this topic. I've extracted the essentials and reposted it in the beta section with instructions.

Posted: Wed Jan 21, 2009 8:48 am

We don't like to delete things, never going to know when they might be useful. Just let it die :)