 |
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
 Posted: Mon Nov 26, 2007 4:53 pm
[2.13] problem with trigger states
|
I have a multistate trigger that worked up through 2.12 but does not now. In the second state, it compares part of the input against a variable. If it matches, it continues. If not, it is supposed to set the state to 1 to wait for the correct match again. Instead, in 2.13, it seems to be setting the state to 0.
The following procedure demonstrates:
#trigger statetest {state test start} {#say test started}
#cond statetest {state test (%w)} {#if (%1 = "A") {#say test A received} {#say test A not received;#state statetest 1}}
#show state test start
(returns: test started)
#show state test A
(so far, so good. returns: test A received)
#show state test start
(returns: test started)
#show state test B
(correct so far. returns: test A not received)
#show state test A
(trigger does not fire! Trigger is not on state 1)
#show state test start
(trigger was on state 0! returns: test started) |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Nov 26, 2007 5:21 pm
|
Even typing "#state statetest 1" on the command line appears to be setting the state to 0 instead of 1.
|
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Tue Nov 27, 2007 6:36 am
|
Confirmed.
|
|
_________________
Asati di tempari! |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Nov 27, 2007 9:01 pm
|
Added to bug list. Not sure what caused this to suddenly break in 2.13...I'm not aware of anything I changed with trigger states, but I'll definitely look into it.
|
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Dec 10, 2007 1:45 pm [2.16] #state always sets to 0
|
This is still a problem in 2.16. The following demonstrates more clearly:
#trigger statetest {test state} {#say state 0 triggered}
#cond statetest {test state} {#say state 1 triggered}
#cond statetest {test state} {#say state 2 triggered}
#cond statetest {test state} {#say state 3 triggered}
#show test state
state 0 triggered
#show test state
state 1 triggered
#show test state
state 2 triggered
#show test state
state 3 triggered
#show test state
state 0 triggered
#show test state
state 1 triggered
#state statetest 3
#show test state
state 0 triggered
#state statetest 2
#show test state
state 0 triggered
#state statetest
#show test state
state 0 triggered
#state appears to be ignoring the second parameter and setting state to 0. The debugging window shows nothing odd. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Dec 11, 2007 6:41 pm
|
Yep, this is still on the bug list. I'll bump the priority up and see what I can do.
|
|
|
|
|
|
|
|
