Next Button Trigger
Jun 08, 2021
Hi all,
I've seen similar posts on this topic but I can't seem to find one that quite matches my issue. I'd like my next button (the yellow chevron in the screen shots) to remain hidden until the user has clicked on specific images. In the first slide, I don't want them to be able to advance to the next slide until they've clicked on the image which opens a PDF of supplemental training material. I set the button's state to hidden when the timeline starts and then added a trigger to change it to normal when the user has clicked the image, but the next button remains hidden. I also tried it with the Disabled state, but it remains disabled. Additionally, I set the timeline event to start on This Slide and on the Next Button but couldn't get either to work.
Similarly, I have slide where I don't want the user to advance until they have clicked on the thought bubbles of the cutout people. I added the conditions to the trigger and have made sure that there are states for each thought bubble for both Selected and Visited; not sure which is the right one, but couldn't get either to work when I added the trigger to change the state of the button back to normal when the conditions were met. I'm sure it's something obvious I'm overlooking here, but the solution continues to elude me! Any guidance is appreciated! Screenshots attached.
8 Replies
Without being able to see your story, I'm pretty much in the dark, but here are a couple of guesses. These are things that could cause what you are seeing, and might actually be causing it.
If you set the initial state of NextButton to Hidden, its timeline doesn't start until the click changes its state to Normal, at which time your trigger changes its state to Hidden. Best practice would be either to set its initial state to Hidden, or Change its state to Hidden when the timeline starts on This Slide. I know a trigger of that sort defaults to the timeline of the same object, but that is seldom the best option.
After that, your trigger to change it to Normal should work when Picture 3 is clicked.
The other one is easier. If NextButton1 is Disabled, or Hidden (either by a trigger, or because its time on the timeline hasn't come yet), you can't click on it. Write your triggers like this:
If those ideas don't work, attach your .story file here, so someone can take a look at why it isn't working.
The fix for the first one worked; many thanks! Added the slide file here for additional help with the second one.
These triggers are almost there
:
Clicking ThoughtKatherine makes it visited; you want NextButton to become normal when ThoughtKatherine is clicked, if ThoughtPavan has already been clicked, is is in Visited state, so change them to :
Here's maybe a simpler way.
Why not remove the triggers to check/change from each button, and combine them into one that checks for visited states of both bubbles?
Scott,
It is simpler, just not as reliable. There are circumstances that cause SL to miss the moment when the last of a series of items becomes "Visited". Testing on the click is more reliable.
That said, the whole concept of using "Visited" is suspect. For example, if the slide is revisited, and is not specifically set to "Return to visited state on Revisit", the Visited state is lost, and the learner has to click both of them again to advance. If it were mine, I would create one or two variables to track whether both layers had been visited, because variables never forget.
This is the best comment thread on the internet. I learn something new every time I come on here. You've saved the day, Walt! Thank you both so much for your input!
Thanks for the follow up Walt. I haven't experienced any circumstances like that, so far. As for the revisiting scenario, I would use a variable to check set/get completion of the interaction and only disable clickables if complete = false.
Anyway, I agree with you Amity - this is one of my favorite user communities for the same reasons,
You're welcome. PIAWYC (Pass it along when you can).