SL2: DIsabling Next button till all other scenes visited
Oct 20, 2017
Hi everyone
I have done some searching around but I cannot get this to work.
I have a slide that has two Groups on there that when you click each one, takes you to different scenes. I want to force the user to have had to click on both and visited both scenes before the Next button becomes available.
The reason I have set these as Groups is because I have created these as a graphic. I have tried setting one of the states of the shapes to Visited when the user clicks the Groups and set a trigger to say when both shapes states are Visited, make the Next button available. I have set the slide trigger to Resume Saved State when revisiting the slide too.
I just cannot seem to get it to work. The next button just will not become active. Don't know if I am missing something but everything looks ok. Please can someone help.
5 Replies
Hi Sachin
can you share the story file - easier for someone to help if we can see the setup.
Hi Wendy
I have tried uploading the file but because of our firewall it wont allow me to :(
I still cannot figure it out and its becoming a bit of a nightmare here. Is there any other way I could share the file?
2 thoughts:
1. Groups do not play nicely with states (or anything else for that matter.) You can recognize people that find ways around using groups in SL; they are happier than those who use them :) Export them as a graphic, and they will work much better.
2. Visited states are reliable pretty much only if you are visiting layers on the same slide. If you are visiting other slides, they may work, and if you are visiting other scenes, almost certainly won't work. For absolute, always works reliability, use variables.
a. Create a T/F variable with a default value of False, for each scene the user must visit.
b. When the timeline on the menu slide starts, hide NEXT button if variable1 is False, OR variable 2 is False, etc. If even one variable is false, the user hasn't visited every scene. Note the menu slide should be set to return to initial state on revisit, to guarantee that the timeline restarts.
c. At the end of scene 1, before the user returns, adjust variable1 to be true, etc.
d. If you want a visual indicator that a section is finished, create a custom state (I name it completed). Write triggers: Change state of menu button 1 to completed when the timeline of the slide starts if variable1 = True, etc. Note: you will be sorry if you use the visited state and write triggers that reference it.
3. Most people that struggle with making things work using the visited state generally have one of two problems. Either they are using "When state of ... is visited (see here for an explanation of why this doesn't work: https://community.articulate.com/discussions/articulate-storyline/changing-the-next-button-based-upon-visited-states-of-only-selected-respsonses ), or they are writing their own triggers using the visited state. You can successfully include the built-in states in your triggers only in the conditions part of the trigger. Writing your own triggers frequently conflicts with the built-in triggers, with unpredictable results.
Chech out the attached sample. the restricted version does what you describe.
Worked like a total charm!! I wish I could send you some chocolates!!! Seriously! Saved me a total headache that I've been having for days. Admittedly, I tripped up at every point i.e. using the visited states, using the built in functions etc. What a learning curve I have had today!!
THANK YOU!
Glad I was able to help you, and somebody here brought me chocolate this AM. Guess you reap what you sow.
PIAWYC (Pass It Along When You Can)
This discussion is closed. You can start a new discussion or contact Articulate Support.