Zugg Software :: View topic - [3.07] Buttons updating/failing to operate with non-updating variable

Magician Joined: 23 Nov 2004 Posts: 364

For the button to stop working:

1. Make a multistate button "test"
2. Make a substate with caption a, put #print blah in as its script
3. go the the main state test -> options -> variable, set variable @buttontest
4. click substate a, see blah printed
5. type #var buttontest 1
6. button will fail to fire when you click on it.

For the button to continually fire without the variable changing:

1. enter this in command line: #tr {this is a test} {#var buttontest 5}
2. Make a multistate button "test"
2. Make a substate with caption a, put #print blah in as its script
3. go the the main state test -> options -> variable, set variable @buttontest
4. click substate a, see blah printed
5. type #show this is a test numerous times
6. blah will keep being printed

The documentation states the button with a variable will fire when its variable state changes.

Posted: Tue May 19, 2009 7:39 am

I'm unable to reproduce this, changing the variable, clicking the button all appear to correctly function.

The only case where the appropriate script was not execute was when clicking state 2, then calling "buttontest = 2", the varible isn't changed so... nothing happens, could be beneficial to execute the script when the variable is set, not changed. Otherwise i could forsee setting a dummy state.. probably state 0, and returning the button to state = after every button click.

Magician Joined: 23 Nov 2004 Posts: 364

The instructions I gave only had one state being created. Also, do you have the button set as a multistate? This doesn't occur with a push button. After testing my instructions, this bug happened again. Also, after performing the latter instructions, if you add an additional state after typing #show this is a test, that state's script will be printed out after the next #show.

1. enter this in command line: #tr {this is a test} {#var buttontest 5}
2. Make a multistate button "test"
2. Make a substate with caption a, put #print blah in as its script
3. go the the main state test -> options -> variable, set variable @buttontest
4. click substate a, see blah printed
5. type #show this is a test numerous times
6. blah will keep being printed
7. Make a new substate b, have it's script print script b
8. type #show this is a test numerous times
9. b is printed
10. Make a new substate c, have it's script print script c
11. type #show this is a test
12. c is printed

The expected behavior to me would be the last called script would be printed, which in this case may be considered the last one made. This is the output I'm getting

Posted: Tue May 19, 2009 5:21 pm

It's the "#var buttontest 5" that is doing it. You are setting the button to a state that doesn't exist yet. In your first test, the button only has one state, and you are trying to set it to state 5. What happens in this case is that the variable gets changed from 1 to 5. Then when CMUD tries to set the button state to 5 and discovers that no such state exists, CMUD changes the variable back to the highest state number available (1 in this case). Since the variable now changed from 5 back to 1, the button script gets executed.

If you change your script to be "#var buttontest 1" then it works as expected and only fires once.

So in any case, what you are doing in your script is undefined. The effect of setting a button state variable to a state that doesn't exist is not defined.