Zugg Software :: View topic

Posted: Thu Oct 26, 2006 9:13 pm

Hey Zugg,

I forgot you asked me to post this. But here is the trigger that keeps failing for me. It was working in the session I manually recreated it, but now it is saying compilation error. PM if you need the original support case number.

One other thing I just noticed, which may help, is that only two of the conditions of this trigger are regular expression triggers. The rest are standard pattern triggers, but in the Package Editor, only the two with Regular Expression said they compiled.

Here's the original code:

Posted: Thu Oct 26, 2006 9:26 pm

Hmmm... I just reviewed the actual source and I'm guessing that the following holds true.

kind = 5 ==> Trigger
opt = 137 ==> Regular zMUD/CMUD pattern
opt = 201 ==> Regex pattern.

That means the code seems to export the options of my triggers correctly, and it is displayed correctly in the Package Editor. If that is the case, I would guess that is being represent and stored correctly, but perhaps the compiler (given on the "+=====+" style of some of the conditions), is try to compile all parts as regular expression patterns.

Posted: Thu Oct 26, 2006 11:06 pm

Remind me what the problem was. I thought I remembered the problem being that you got a parsing error when entering it into the command line, but not when entering it into an alias in the settings editor.

But I just pasted your multiline command into the command line and it worked just fine. I don't think I've fixed anything in the parser recently, so maybe I just don't remember what the problem was.

So remind me if the problem was with a syntax error, or if it's something more related to the trigger actually working or not. If it's the trigger not working properly, then also post some sample text for testing the trigger.

Posted: Fri Oct 27, 2006 5:03 am

It temperamental really sometimes it works and sometimes it doesn't. I haven't tried from the command line for a while but in the settings editor it gives and error. Also the trigger itself doesn't fire. If you look at the compiled tab in the Package Editor most of the states don't compile. If you get it working once, exit CMUD and try to access it again. It won't seem to work then.

Posted: Fri Oct 27, 2006 11:41 pm

Well, I discovered a couple of interesting things about this.

First, the errors when clicking the compiled tab were fake. The compiled code tab was displaying an error message whenever the script was empty. So this was just an issue with the settings editor and not actual errors in your script.

However, the big error that I discovered is that when trigger states are initially loaded, CMUD didn't actually know what the state types were. Actually, it was caching a value of zero for the state type instead of loading it from the database the first time. If you went into the settings editor and changed the state to something else, then back again, then it would work. This bug might also have been effecting some properties of button states.

Anyway, I've got this fixed in v1.12 and it looks like trigger states work. I've also been able to add a nice visual indicator in the settings editor to show which state is currently active when you expand the main trigger to see the sub-states.

Posted: Sat Oct 28, 2006 5:00 am

That's great news Zugg, and I'm glad you got that one tracked down. I'm sure it would have come up more often with other folks. Looking forward to tomorrows release.