On slide 1, I have created several hot spots, over individual text boxes that the user can click (using the hot spots) to take them on different learning paths.
I would like, once the user returns to slide 1, for the text box to change to a "visited" state.
My problem is: my hot spots have to cover the text box entirely, so I don't know how to signify to Storyline that the user has clicked on anything to signify the state change.
Not seeing your actual module, some of what I say may not be valid. But...
One simple solution, if your activity allows it, would be to eliminate the hotspots, and set up triggers for the text boxes to branch as desired. Assuming you've already got the Visited state set up for the text boxes, clicking the text boxes would automatically set their states to Visited.
If you need to keep the hotspots, another thing you could do would be to add a trigger for each hotspot to set the state of the associated text box to Visited. Just make sure to move that trigger up in the order so that it comes before the trigger to branch to the selected path.
You could also do this with T/F variables.
You'll probably want to set the slide to resume its saved state when revisiting.
2 Replies
Hi Greg,
Not seeing your actual module, some of what I say may not be valid. But...
One simple solution, if your activity allows it, would be to eliminate the hotspots, and set up triggers for the text boxes to branch as desired. Assuming you've already got the Visited state set up for the text boxes, clicking the text boxes would automatically set their states to Visited.
If you need to keep the hotspots, another thing you could do would be to add a trigger for each hotspot to set the state of the associated text box to Visited. Just make sure to move that trigger up in the order so that it comes before the trigger to branch to the selected path.
You could also do this with T/F variables.
You'll probably want to set the slide to resume its saved state when revisiting.
Thanks, David.
That worked perfectly.
This discussion is closed. You can start a new discussion or contact Articulate Support.