Hi all,
\n
\n
I'm trying to figure out how to change a button state when you click on it, then change it back to the original state when you click it again. It seems simple, but it just won't work for me, and I'm hoping someone here will tell me where I'm going wrong. I've included the file with this post.
\n
All I want is to when I click on the button (starts off in the \"Off\" state) to change to a new state (ie \"On\" state), but then when I click it again, it switched back to the original state (ie the \"Off\" state).
\n
Currently, I can get it to change once to the \"On\" state, but it won't change back to the \"Off\" state when I click it again. I've added a tracking T/F variable called \"buttonOn\" as a way of controlling the state of the button. The button (called OnOff Button) has two states: Normal and buttonOn)
\n
\n
Here are the triggers I've got in the order they appear:
\n
1) Set buttonOn to value True
\n
When the state of OnOff Button is buttonIsOn
\n
\n
2) Set buttonOn to value False
\n
When the state of OnOff Button is Normal
\n
\n
3) Set state of OnOff Button to Normal -----> (ie State 1)
\n
When the user clicks OnOff Button
\n
If buttonOn = value True
\n
(ie change the button to be Off when the user clicks the button and visual state of the button is On)
\n
4) Set state of OnOff Button to buttonIsOn ----> (ie State 2)
\n
When the user clicks OnOff Button
\n
If buttonOn = value False
\n
(ie change the button to be On when the user clicks the button and the visual state of the button is Off)
\n
Seems logical to me, but it doesn't work. I can get it to change once, but it won't change back to the original state. I can do it using layers, but I'd rather stick with changing states.
\n
\n
What am I doing wrong?
\n
i've noticed that when I try editing the different states, there are triggers that appear where I can't delete them. Is this normal?
\n
Hi all,
\n
\n
I'm trying to figure out how to change a button state when you click on it, then change it back to the original state when you click it again. It seems simple, but it just won't work for me, and I'm hoping someone here will tell me where I'm going wrong. I've included the file with this post.
\n
All I want is to when I click on the button (starts off in the \"Off\" state) to change to a new state (ie \"On\" state), but then when I click it again, it switched back to the original state (ie the \"Off\" state).
\n
Currently, I can get it to change once to the \"On\" state, but it won't change back to the \"Off\" state when I click it again. I've added a tracking T/F variable called \"buttonOn\" as a way of controlling the state of the button. The button (called OnOff Button) has two states: Normal and buttonOn)
\n
\n
Here are the triggers I've got in the order they appear:
\n
1) Set buttonOn to value True
\n
When the state of OnOff Button is buttonIsOn
\n
\n
2) Set buttonOn to value False
\n
When the state of OnOff Button is Normal
\n
\n
3) Set state of OnOff Button to Normal -----> (ie State 1)
\n
When the user clicks OnOff Button
\n
If buttonOn = value True
\n
(ie change the button to be Off when the user clicks the button and visual state of the button is On)
\n
4) Set state of OnOff Button to buttonIsOn ----> (ie State 2)
\n
When the user clicks OnOff Button
\n
If buttonOn = value False
\n
(ie change the button to be On when the user clicks the button and the visual state of the button is Off)
\n
Seems logical to me, but it doesn't work. I can get it to change once, but it won't change back to the original state. I can do it using layers, but I'd rather stick with changing states.
\n
\n
What am I doing wrong?
\n
i've noticed that when I try editing the different states, there are triggers that appear where I can't delete them. Is this normal?
\n
Hi Doug, I saw your comment about your posts being reported right away. Not sure what is causing that but I'll look into it.
For your button, a quick fix is to switch your buttonison state to the built-in selected state. With the selected state, you don't need triggers for it to work, and you can still have variables that track the button state if you need that. I've attached an example. Hope this helps. Please let me know if you have any questions!
Hi Doug, I saw your comment about your posts being reported right away. Not sure what is causing that but I'll look into it.
For your button, a quick fix is to switch your buttonison state to the built-in selected state. With the selected state, you don't need triggers for it to work, and you can still have variables that track the button state if you need that. I've attached an example. Hope this helps. Please let me know if you have any questions!
Yup, that definitely fixed the problem. Thanks, Ginger ! :-)
Yup, that definitely fixed the problem. Thanks, Ginger ! :-)
