I've tried everything possible to make this work, but either it's a bug or I'm missing something. I have a slide with two icons on it. When the user clicks each icon, a layer appears. I want the Next button on the slide to show when both layers were visited. I tried many ways to make this work by using triggers and variables, but the Next button always shows after I click one of the icons for the second time. They both show as visited, but the Next button does not work. Can somebody help me figure it out? Have you had this button behavior before? What could be wrong? Thank you!
You must be using SL3? I can't open it with my SL2, sorry.
I'm guessing it has to do with the sequence of your triggers and when you set each variable. Rather than showing the Next button when both layers are visited, try showing it when both icons have been visited.
I use Articulate 360. That's actually how it's set - for the icons to be visited. I even deleted the whole slide and built it again from scratch, still not working. ;-(
Ok, now it works, but when I come back to this slide, the Next button is disabled again.
I have a background image with two icons from the Articulate Icon library. Their background is set to no fill and trigger set to change state to fill with 50% opacity when visited. The next button is disabled until icons state changes to visited with variables for both layers. The variables are set to equal to true when the timeline on the layer starts.
Sorry for the confusion on this one. There's currently a bug that's causing you to see the odd behavior upon returning to that slide. I've reported it to the support team and we'll get it on the list for a fix.
Typically, you'd only need to set up the triggers to evaluate the visited states and then things would work great upon returning to the slide again. So your original approach was correct.
And your intended fix using variables is a great workaround while we wait for the bug to get addressed. In this case, you'd set up a trigger to evaluate your two T/F variables upon returning to the slide. If both variables are equal to, say, True, then you'd change the state of the next button to normal.
I've updated your .story file and am attaching it here with the workaround.
This might simplify things a bit. I don't think you need any variables.
Use a slide trigger that says to enable the Next button when the state of the two icons are Visited. That would get rid of your variables (which are causing some of your problems I think).
Also include a slide trigger to disable the Next button when the timeline starts with the condition If the two icons are not visited.
Finally, be sure your slide property is set to Resume Saved State so that when you revisit the slide the Next button is still enabled.
That's a great workaround Chris and neat way to rethink the triggers. The original trigger method should still work and needs to be fixed, but this is certainly tidier than the variables solution.
Michaela, I've altered the file to show the workaround Chris mentions. It's attached below.
A quick update, a fix for the issue with the next button returning to a disabled state upon revisiting a slide is now also included in the latest update for Storyline 3. Updates are free for Storyline 3 licensees and you can download the latest update here. You can also view the entire list of Release notes for Storyline 3 here.
12 Replies
Hi Michaela -
Could be several things. If you can upload the file, I'll take a quick look and see what's going on.
Chris
Thank you, Chris. Here it is.
You must be using SL3? I can't open it with my SL2, sorry.
I'm guessing it has to do with the sequence of your triggers and when you set each variable. Rather than showing the Next button when both layers are visited, try showing it when both icons have been visited.
I use Articulate 360. That's actually how it's set - for the icons to be visited. I even deleted the whole slide and built it again from scratch, still not working. ;-(
OK. Tell me a little more about your setup. What are you using for icons and where is the trigger located?
Ok, now it works, but when I come back to this slide, the Next button is disabled again.
I have a background image with two icons from the Articulate Icon library. Their background is set to no fill and trigger set to change state to fill with 50% opacity when visited. The next button is disabled until icons state changes to visited with variables for both layers. The variables are set to equal to true when the timeline on the layer starts.
Hi Michaela,
Sorry for the confusion on this one. There's currently a bug that's causing you to see the odd behavior upon returning to that slide. I've reported it to the support team and we'll get it on the list for a fix.
Typically, you'd only need to set up the triggers to evaluate the visited states and then things would work great upon returning to the slide again. So your original approach was correct.
And your intended fix using variables is a great workaround while we wait for the bug to get addressed. In this case, you'd set up a trigger to evaluate your two T/F variables upon returning to the slide. If both variables are equal to, say, True, then you'd change the state of the next button to normal.
I've updated your .story file and am attaching it here with the workaround.
Please let me know if you have any questions!
Mike
This might simplify things a bit. I don't think you need any variables.
Use a slide trigger that says to enable the Next button when the state of the two icons are Visited. That would get rid of your variables (which are causing some of your problems I think).
Also include a slide trigger to disable the Next button when the timeline starts with the condition If the two icons are not visited.
Finally, be sure your slide property is set to Resume Saved State so that when you revisit the slide the Next button is still enabled.
Sweet!
That's a great workaround Chris and neat way to rethink the triggers. The original trigger method should still work and needs to be fixed, but this is certainly tidier than the variables solution.
Michaela, I've altered the file to show the workaround Chris mentions. It's attached below.
Mike
Thanks Mike. Always looking to Simplify, Simplify. :-)
Hi all,
A quick update, a fix for the issue with the next button returning to a disabled state upon revisiting a slide is now also included in the latest update for Storyline 3. Updates are free for Storyline 3 licensees and you can download the latest update here. You can also view the entire list of Release notes for Storyline 3 here.
Please let us know if you have any questions!
Thanks Ashley!
This discussion is closed. You can start a new discussion or contact Articulate Support.