Hi there! I really loved this idea of disabling the next button until users complete various actions before proceeding. I want to recreate in a course that I am building and have set it up the exact same way and it doesn't seem to work.
I have it set up as slides within a scene, and another set up to take users between screens and the next button never returns to it's normal state.
Any idea what I am missing? Here is the demo, and attached is the Storyline file.
Hi Ashraf, the problem still exists. For whatever reason if you preview the slide it works fine but if you preview the scene or the entire project it doesn't work.
That's why I'm stumped, because if the slide preview works it should work across the board, but it doesn't.
There was another small thing. You don't have to precise on the previous button in slide 3.4, 3.5 etc that jump to 3.2 because storyline remembers where you were so it will take you automatically towards 3.2. It's working now, check new file
I looked at your file, and I suggest to use another method... If you look the attachment, here is what I did:
- On your menu slide, I deleted the trigger which disable the next button, - I added true/false variables for each square... They will work the same than the visited state, but as your course jumps from scene to scene, variables are more stable than objects' states (which depends on the revisiting options)... Basically, they are switches. - I added two trigger on the next button: *Every trigger as some conditions... Those conditions are based on the value of each variable *The first one shows a layer that tell the user he must see every content before continuing. It will be shown if any of the three true/false variables is equal to "false". *The second one jump ton next slide... It works only if the three variables are equal to true... - I added trigger on each square that change the value of a variable when the user clicks, and then jump to the layer (order is important here)... - I changed the revisiting options in the base layer's options of the main slide to Resume saved state.
And that's it... I think the problem came from the trigger which was disabling the next button at the start of the sequence... Therefor, every time you were coming back on the main slide, the next button was disabling again... In the demo you shred, conditions are on the same slide (contents is on layers), but in your case you jump to other scenes... So every time you revisit the main slide, you're reseting the conditions... It's an endless loop...
Thanks Cedric! I think this will work. I haven't used true/false variables before and it look like I need to learn more about them! What you are saying about the state of objects and their conditions as you move between scenes makes perfect sense.
9 Replies
Hi Valerie
Can you share the story file?
That would probably be helpful! Just added on to the initial thread as an attachment.
There was nothing wrong, I just changed the order of the triggers and it's working fine.
Look at your file in attachement
Hi Ashraf, the problem still exists. For whatever reason if you preview the slide it works fine but if you preview the scene or the entire project it doesn't work.
That's why I'm stumped, because if the slide preview works it should work across the board, but it doesn't.
There was another small thing. You don't have to precise on the previous button in slide 3.4, 3.5 etc that jump to 3.2 because storyline remembers where you were so it will take you automatically towards 3.2.
It's working now, check new file
Let me know if it helped
Regards
Nope, still the same problem. Preview the entire project and you'll see what I mean.
Hi Valery,
I looked at your file, and I suggest to use another method... If you look the attachment, here is what I did:
- On your menu slide, I deleted the trigger which disable the next button,
- I added true/false variables for each square... They will work the same than the visited state, but as your course jumps from scene to scene, variables are more stable than objects' states (which depends on the revisiting options)... Basically, they are switches.
- I added two trigger on the next button:
*Every trigger as some conditions... Those conditions are based on the value of each variable
*The first one shows a layer that tell the user he must see every content before continuing. It will be shown if any of the three true/false variables is equal to "false".
*The second one jump ton next slide... It works only if the three variables are equal to true...
- I added trigger on each square that change the value of a variable when the user clicks, and then jump to the layer (order is important here)...
- I changed the revisiting options in the base layer's options of the main slide to Resume saved state.
And that's it... I think the problem came from the trigger which was disabling the next button at the start of the sequence... Therefor, every time you were coming back on the main slide, the next button was disabling again... In the demo you shred, conditions are on the same slide (contents is on layers), but in your case you jump to other scenes... So every time you revisit the main slide, you're reseting the conditions... It's an endless loop...
I hope it helps! On my side, at last, it works!
Thanks Cedric! I think this will work. I haven't used true/false variables before and it look like I need to learn more about them! What you are saying about the state of objects and their conditions as you move between scenes makes perfect sense.
Thank you!
My pleasure!
Here is a ressource which could help you understand what variables are: https://community.articulate.com/series/5/articles/working-with-variables
As you can see at the end of the article, state can only track in the same slide... So in your case, variables are needed to work as states... :)
This discussion is closed. You can start a new discussion or contact Articulate Support.