Forum Discussion
Trigger with Conditions
Hi all,
I'm just learning SL and am currently stuck on a trigger that uses conditions. I want the Next image to appear once the user completes each interaction on the slide. They have to click four buttons to make four definitions appear and then the Next image should appear. The interactions work fine but I cannot get the Next button to appear when I want to. My story file is attached.
Thank you in advance!
Jennifer
JennyAnnRowe : The conditions on your trigger are fine. The problem is the that it's set to run when the timeline starts.
The timeline starts before the user can interact with the slide. So the only way that would run is if the user finished the interaction, navigated to the previous slide, and then returned to this interaction.
Thus, you need to set up the trigger like the example in my previous reply, with the "when" being when all the objects reach a given state. You can use the state of the definitions instead of the buttons.
By the way, you can edit your original trigger so it disables the Next button:
- Change the set state to Disabled.
- Change the conditions to ≠ Normal (or = Hidden).
- Change the connections to "or," so that the trigger will run if any of the definitions is still hidden.
Hi Jennifer,
I don't see the attached file. Would you please try again to attach it?
As Kendall said, the file wasn't attached.
Based only on your description, it sounds like the conditions could be that all 4 buttons are in the Visited state. That would look something like this:
Note that if there's a trigger that disables Next when the timeline starts, that will also need conditions to prevent it from running if the user returns to the slide after completing the interaction.
This post might help: TIP: Controlling the NEXT Button 101 | Articulate - Community
There is no file attached.
Hi Kendal, Judy, and Michael,
Thank you for your responses and my apologies for the attachment - not sure what happened there. I'm reattaching the file now. Judy, your condition State is different from what I was using and I wonder if that is the problem.
JennyAnnRowe : The conditions on your trigger are fine. The problem is the that it's set to run when the timeline starts.
The timeline starts before the user can interact with the slide. So the only way that would run is if the user finished the interaction, navigated to the previous slide, and then returned to this interaction.
Thus, you need to set up the trigger like the example in my previous reply, with the "when" being when all the objects reach a given state. You can use the state of the definitions instead of the buttons.
By the way, you can edit your original trigger so it disables the Next button:
- Change the set state to Disabled.
- Change the conditions to ≠ Normal (or = Hidden).
- Change the connections to "or," so that the trigger will run if any of the definitions is still hidden.
Ah, thanks again, Judy. I am struggling to wrap my head around the logic of some triggers. I really appreciate your instruction. As for the player controls, I want to remove them altogether because some slides in the course auto-advance and some require manual advance. An inoperative control will confuse and frustrate the student so I am just going to use a Next button when the student has to advance manually.
Continuing with Jennifer's question, is there a way to make it so that all conditions are already met when user revisits the slide? Say they need to view all content prior to moving on the first time, but then they want to go back to the slide and quickly review certain content. In my project, all works well the first time through the slide, but when I select the back button in my scene, and then attempt to go forward again, the next button remains disabled, even if I view all of the content again. Thanks so much for any help!
Add conditions to the trigger that Disables the Next button so that trigger will only run before the enabling conditions are met.
- For example, let's say that 3 buttons need to have their state = Visited to enable Next.
- The trigger to disable Next would have conditions that the buttons ≠ Visited.
For reference:
- TIP: Controlling the NEXT Button 101 | Articulate - Community
- Also, this User Guide article has info about conditions: Storyline 360: Working with Triggers | Articulate - Community
If you have other questions, you should start a new discussion.
