I'm using a trigger to change the state of the next button to enable when the state of 3 objects are visited. This has worked well in the past. I now have one slide where the next button is enabled as soon as 2 of the 3 objects have been visited even though I have selected all 3 objects. Has anyone seen this and know what the issue is? I have tried recreating the trigger to no success.
I am not able to load the Storyline file because it has proprietary information.
I just did a quick test (using the latest version of SL360) and everything works as expected for me. Maybe you can share a screenshot of the trigger panel and the Change State trigger setup.
I've add pictures of a first the slide that doesn't work and then a slide that's very similar that does work. This logic has worked on every slide I've used it on except for this Course Menu slide where it doesn't wok.
OK. I created a new project that has just the bare bones with the slide that doesn't work. I think it stopped working when I added the triggers for the boxes above the images.
As it is, they all have to be Not Visited, or the whole condition is false, and the Next button is not disabled. By using OR, you disable it if even one of them is not visited.
Personally, I think if this trigger works:
it is only because you got lucky. I would change it to "when timeline starts, on condition" that all of them are visited.
5 Replies
I just did a quick test (using the latest version of SL360) and everything works as expected for me. Maybe you can share a screenshot of the trigger panel and the Change State trigger setup.
I've add pictures of a first the slide that doesn't work and then a slide that's very similar that does work. This logic has worked on every slide I've used it on except for this Course Menu slide where it doesn't wok.
OK. I created a new project that has just the bare bones with the slide that doesn't work. I think it stopped working when I added the triggers for the boxes above the images.
Change the ANDs in this trigger to ORs.
As it is, they all have to be Not Visited, or the whole condition is false, and the Next button is not disabled. By using OR, you disable it if even one of them is not visited.
Personally, I think if this trigger works:
it is only because you got lucky. I would change it to "when timeline starts, on condition" that all of them are visited.
Thanks for catching this. I've obviously been looking at this for way too long.
This discussion is closed. You can start a new discussion or contact Articulate Support.