I have a slide with 7 rectangles on it, with various states, and each one lightboxes to a quiz slide.
I would like to use a completed state, in place of a visited state, so each rectangle would show completed when the appropriate variable on the quiz slide is equal to true. I am testing this with the “Loss of water flow” rectangle, but for some reason, the quiz variable is not setting to True and I am not sure why. Is it because the quiz slides are lightboxed?
I have cut my project so it is only showing the needed slides.
The submit action must be the last trigger on the submit button. Otherwise, the submit action takes over, and no other action is performed.
Since the WLCYK variable changes on a different slide (the quiz slide), the main menu slide can't see it change, so the trigger to change the sticky note never fires.
There needs to be some action that occurs on that slide to initiate the trigger to change the state of the sticky note, and I can't think of any that work. Maybe some genius will weigh in with an idea.
If not, you may have to reconsider lightboxing the quizzes. If you just jump to them, (instead of lightbox,) then jump back, you can set this trigger to fire when the main menu timeline starts. That is an action a trigger can see, and it will fire.
To keep the audio from playing each time it starts, you can set the audio to play when the timeline starts, if audio211Complete is not = True.
I added this to my full project, but when I now come back to the slide (Slide 2.11 after taking one quiz question, the rest of the rectangles are disabled again.
Thanks for your patience as we investigate the issue associated with the next button not being normal/accessible on a revisit to a slide where you had initially set it to hidden at the start of the slide. It’s been determined that this behavior is as expected based on what the triggers are telling Storyline, although it may not match what you wanted to occur.
Since the previous/next buttons are set to be hidden at the start of the slide via triggers, when returning to the slide the command given to Storyline is to hide the buttons as soon as the slide starts. The slide is resuming the saved state of the previous/next buttons as expected, but then the triggers tell Storyline to hide them as soon as the slide loads.
This is where applying the conditions to those initial triggers will come into play - as you’ll want to adjust the next/previous buttons to “hidden” only if the user has not visited this slide before. You’ll see this set up in the file I attached that has that trigger/condition set up associated with the state change of the next player button.
Please let us know if you have any other questions!
6 Replies
2 things
The submit action must be the last trigger on the submit button. Otherwise, the submit action takes over, and no other action is performed.
Since the WLCYK variable changes on a different slide (the quiz slide), the main menu slide can't see it change, so the trigger to change the sticky note never fires.
There needs to be some action that occurs on that slide to initiate the trigger to change the state of the sticky note, and I can't think of any that work. Maybe some genius will weigh in with an idea.
If not, you may have to reconsider lightboxing the quizzes. If you just jump to them, (instead of lightbox,) then jump back, you can set this trigger to fire when the main menu timeline starts. That is an action a trigger can see, and it will fire.
To keep the audio from playing each time it starts, you can set the audio to play when the timeline starts, if audio211Complete is not = True.
See the attached version.
Thank you Walt.
I added this to my full project, but when I now come back to the slide (Slide 2.11 after taking one quiz question, the rest of the rectangles are disabled again.
Try setting that slide to Resume saved state when revisiting, and see if that helps.
It does help, but then when I move past the slide to the next slide and go back to it, I do not see the Next button.
https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=d47628db-5057-42eb-a8f5-acb0820f330d
Hi Melissa,
I know we had discussed the issues with the next button in the hidden state previously? Did you update this course using the variable method as well?
Hi all,
Thanks for your patience as we investigate the issue associated with the next button not being normal/accessible on a revisit to a slide where you had initially set it to hidden at the start of the slide. It’s been determined that this behavior is as expected based on what the triggers are telling Storyline, although it may not match what you wanted to occur.
Since the previous/next buttons are set to be hidden at the start of the slide via triggers, when returning to the slide the command given to Storyline is to hide the buttons as soon as the slide starts. The slide is resuming the saved state of the previous/next buttons as expected, but then the triggers tell Storyline to hide them as soon as the slide loads.
This is where applying the conditions to those initial triggers will come into play - as you’ll want to adjust the next/previous buttons to “hidden” only if the user has not visited this slide before. You’ll see this set up in the file I attached that has that trigger/condition set up associated with the state change of the next player button.
Please let us know if you have any other questions!
This discussion is closed. You can start a new discussion or contact Articulate Support.