I was wondering if anyone else had experienced this as I have on several occasions: if I set a trigger to say "....if all of buttons are equal to visited" but this never seems to work for me and I have to delete it in favour of creating a number variable instead. Can anyone shed any light on this?
Two thoughts - One is that if the slide is set to Reset to initial value, or Choose, on revisit, you can lose the visited state. Sometimes even Keep saved state can lose visited states if you visit a complex number of slides before returning.
The other is that if you are the using "states are visited" in the WHEN portion of the trigger instead of the IF portion. The state of an object is not an action, so it can't really trigger an action in the WHEN portion.
I tried to create some test examples but Sod's Law dictates that it's working fine. I'll update when I come across it again. Thanks for your responses though
It's happened - I have an example! Just bear with it for a couple of layers - you don't need to read the content.
The final slide layer I initially set up to but the final slide layer should show a "Click 'Next' to continue" once all the buttons are visited, but this didn't work.
I set up a T/F variable to show this button once all the buttons were visited. Still doesn't work.
Try using the opposite value as the state (a double negative). So instead of setting it to "if all buttons = visited...", try "if state is not equal to normal". Articulate is weird like that.
Right I tried this and it didn't work but I got around it by creating a number variable instead - thanks for the advice/help. Good tip below for the built-in variables :)
Are you using the appropriate OR/AND condition for each state that is required to trigger a state change in another object? For example, if there are specific correct states in your frame that are required in order to trigger a state change in something else, each "if" statement must be AND so that it is literal.
On the other side of that, all other object states that are incorrect must be set to "OR".
IMHO, using variables complicates things if they aren't needed, but if that is the only way to get it to work, then so be it.
not sure why the visited state of the buttons aren't working or the variable triggers...so I disabled those triggers and added offstage objects to control the continue button. As the user clicks a button, the offstage object changes to visited...then I used the visited state of all the offstage objects in the triggers and it appears to be working as expected...see this Peek
14 Replies
Hi Charlie
do you have a sample file you can share so we can see the setup.
Two thoughts - One is that if the slide is set to Reset to initial value, or Choose, on revisit, you can lose the visited state. Sometimes even Keep saved state can lose visited states if you visit a complex number of slides before returning.
The other is that if you are the using "states are visited" in the WHEN portion of the trigger instead of the IF portion. The state of an object is not an action, so it can't really trigger an action in the WHEN portion.
I tried to create some test examples but Sod's Law dictates that it's working fine. I'll update when I come across it again. Thanks for your responses though
It's happened - I have an example! Just bear with it for a couple of layers - you don't need to read the content.
The final slide layer I initially set up to but the final slide layer should show a "Click 'Next' to continue" once all the buttons are visited, but this didn't work.
I set up a T/F variable to show this button once all the buttons were visited. Still doesn't work.
Help!
Yes thanks Wendy if you have the time to check the attachment in the thread and let me know your thoughts that would be lovely
Looks broken. When state of triggers. What is really odd if you take the triggers off the buttons it works fine. But I cannot see anything wrong.
I know right? I'm stumped
Try using the opposite value as the state (a double negative). So instead of setting it to "if all buttons = visited...", try "if state is not equal to normal". Articulate is weird like that.
Not equal to normal is not useful with built-in states as most built-in states will validate as normal, often better to use not equal to selected.
Agreed. Use "not equal to selected" as the criterion.
Right I tried this and it didn't work but I got around it by creating a number variable instead - thanks for the advice/help. Good tip below for the built-in variables :)
Are you using the appropriate OR/AND condition for each state that is required to trigger a state change in another object? For example, if there are specific correct states in your frame that are required in order to trigger a state change in something else, each "if" statement must be AND so that it is literal.
On the other side of that, all other object states that are incorrect must be set to "OR".
IMHO, using variables complicates things if they aren't needed, but if that is the only way to get it to work, then so be it.
Hi Charlie
not sure why the visited state of the buttons aren't working or the variable triggers...so I disabled those triggers and added offstage objects to control the continue button. As the user clicks a button, the offstage object changes to visited...then I used the visited state of all the offstage objects in the triggers and it appears to be working as expected...see this Peek
Updated file attached
Amazing Wendy thanks so much! Thanks everyone else for your help too.
Gosh Storyline is quirky sometimes
This discussion is closed. You can start a new discussion or contact Articulate Support.