So, I've inserted a trigger onto a button which changes its state to 'visited' (greyed-out) as well as jumps to another slide once it has been clicked (users return to the slide later). However, even though I have the slide set to 'automatically decide' when revisiting (I've also tried it with 'resume saved state'), when I return to this slide, the button is in its 'normal state' not visited state. When I preview the side on its own it works. When I preview the entire project it doesn't work.
I need to finish this course very soon so any help is greatly appreciated!
If you can't get it to work what you could do is create a true/false variable and set the variable to true when the learner clicks the button. Then have a trigger than checks the variable when the slide starts and if it's true change the state of the object.
For sure, you want to delete the trigger that changes the state to "Visited". There is a built-in trigger that changes the state of an object to "Visited" when it is clicked, if the object has a Visited state. If you write a trigger to do the same thing, they will conflict with each other with results that are strange and (sometimes, but not often) wonderful.
As mentioned above, we'd want to take a look at the .story file and if you're using the visited state as Walt mentioned you could use the behavior of the general "visited" set up to allow it to work based on the descriptions here.
If you want to upload your file, please use the "add attachment" button at the bottom of the reply window to share here.
5 Replies
Hi Bill
it would be helpful if you could upload your .story file - easier to see your setup and try to help you.
If you can't get it to work what you could do is create a true/false variable and set the variable to true when the learner clicks the button. Then have a trigger than checks the variable when the slide starts and if it's true change the state of the object.
For sure, you want to delete the trigger that changes the state to "Visited". There is a built-in trigger that changes the state of an object to "Visited" when it is clicked, if the object has a Visited state. If you write a trigger to do the same thing, they will conflict with each other with results that are strange and (sometimes, but not often) wonderful.
Hi Bill,
As mentioned above, we'd want to take a look at the .story file and if you're using the visited state as Walt mentioned you could use the behavior of the general "visited" set up to allow it to work based on the descriptions here.
If you want to upload your file, please use the "add attachment" button at the bottom of the reply window to share here.
Walt's suggestion solved the problem. Thank you for all the help!
This discussion is closed. You can start a new discussion or contact Articulate Support.