I am new to Storyline 2 but am having trouble getting the Next button to continue after I set a trigger for all buttons to be visited before continuing on. I have looked at several tutorials and not sure what I'm doing wrong. I set a T/F variable set to false, a trigger that changes variable to true after buttons are visited, and a condition to the Next button trigger that equals true to continue.
I have attached my Storyline file. Particularly look at slides 1.3, 2.3, 4.2, and 5.1.
you are setting your state to 'down' when the user clicks but your trigger from the variable is set to when the state is 'visited'. I changed the top trigger to be when state of all buttons is 'down' and it works.
Look at your other slides based on this logic and see how you go...shout out if you need more help
Thanks, Wendy, that did solve most of my issues. Now, I am having trouble with a slider and my trigger that prevents users from advancing until they have clicked the slider to the end. Could someone look at slide 5.1 and see what I am doing wrong?
Also, when I publish it and view in a browser (both Firefox and Explorer), I have to click on the Next button multiple times for slides with no prohibitive triggers to advance. It can range from 2-8 clicks before it will advance. I do have the player menu set to restrictive.
In SL2, the next button won't advance until the timeline ends if you have your Menu navigation set to restricted or locked - so you'll need to take a look at two things - your Player menu options. Go to Player > Menu > Cog wheel and you'll see this option box:
Also look at the length of your timelines on slides - maybe some need tweaking.
I'll take a look at your slide issue now
If you need to have restricted menu navigation there is a workaround - just search on 'Bobbi Bailey' and you will find a detailed workaround to help you
Thanks for the insights. I adjusted the timeline on some of the slides and changed my value to 1 on the slider which solved my issues. Very happy to move forward with this project. Thanks again for your help.
Hi, I have encountered an issue with one of my Storyline SCORM Packages on Blackboard Learn 9.1 using Firefox Quantum 67.0.04 (64 bit). When I click on the Next button on the first slide, it won't jump to the next slide. The wheel just keeps on spinning. At first, the trigger for the Next button in the player was set to "Next Slide". Due to the issue described, I changed the trigger to the specific next slide, which is Slide 1.2. However, this did not fix the issue. Please refer to the attached screenshots.
The issue is only observed in Firefox. However, I can move forward from Slide 1.1 to Slide 1.2 on Chrome even with the trigger for the Next button in the player being set to "Jump to" and "Next slide".
It would be ideal to fix the issue on Firefox because we do not want to confuse our students and lecturers. We recommend Firefox for running Blackboard Collaborate Ultra sessions because there are webcam issues on Chrome using the virtual classroom tool.
Hi Nijel. I see that Vevette is working on your case for this issue and has asked a follow up questions. Thanks for sending us those steps and details! You can reply to her email.
Feel free to update this discussion with any solutions you discover.
Hi Crystal, thanks for your reply. I've provided the SL2 source file to Vevette. She has been given access to my Blackboard development course. I've tried changing different player and slide settings along with different SCORM Player Behaviour settings in Blackboard Learn. None of these combinations solved the spinning wheel issue. It's frustrating, but I won't let it win.
I checked in on your case this AM and saw you and Vevette were able to isolate the issue to some images in the course that you were looking at removing. I hope that helps, but please feel free to let either of us know if you need more help!
15 Replies
Hi Amy
have just looked at 1.3
you are setting your state to 'down' when the user clicks but your trigger from the variable is set to when the state is 'visited'. I changed the top trigger to be when state of all buttons is 'down' and it works.
Look at your other slides based on this logic and see how you go...shout out if you need more help
Hi Amy! Looks like Wendy is assisting you here :)
Thanks, Wendy, that did solve most of my issues. Now, I am having trouble with a slider and my trigger that prevents users from advancing until they have clicked the slider to the end. Could someone look at slide 5.1 and see what I am doing wrong?
Also, when I publish it and view in a browser (both Firefox and Explorer), I have to click on the Next button multiple times for slides with no prohibitive triggers to advance. It can range from 2-8 clicks before it will advance. I do have the player menu set to restrictive.
Here's an updated version of the file.
Many thanks-
Hi Amy
In SL2, the next button won't advance until the timeline ends if you have your Menu navigation set to restricted or locked - so you'll need to take a look at two things - your Player menu options. Go to Player > Menu > Cog wheel and you'll see this option box:
Also look at the length of your timelines on slides - maybe some need tweaking.
I'll take a look at your slide issue now
If you need to have restricted menu navigation there is a workaround - just search on 'Bobbi Bailey' and you will find a detailed workaround to help you
Hi Amy
so the slider has 3 points. Are you saying they can advance to next slide if they only move the slide one place, or two places and not all 3?
I would like for users to click on all three.
Thanks, Wendy!
Hi Amy
I think the issue is the way the slider is set up.
Should the initial setting be at 4? Meaning the slider starts at the right hand side and users are sliding to the left to get the information?
?
Hi Amy,
Here is the thread I believe Wendy was referencing in terms of Bobbi's work around for restricted navigation.
Thanks for the insights. I adjusted the timeline on some of the slides and changed my value to 1 on the slider which solved my issues. Very happy to move forward with this project. Thanks again for your help.
Thanks Amy for the update and I'm glad that assisted you.
This post was removed by the author
Hi, I have encountered an issue with one of my Storyline SCORM Packages on Blackboard Learn 9.1 using Firefox Quantum 67.0.04 (64 bit). When I click on the Next button on the first slide, it won't jump to the next slide. The wheel just keeps on spinning. At first, the trigger for the Next button in the player was set to "Next Slide". Due to the issue described, I changed the trigger to the specific next slide, which is Slide 1.2. However, this did not fix the issue. Please refer to the attached screenshots.
The issue is only observed in Firefox. However, I can move forward from Slide 1.1 to Slide 1.2 on Chrome even with the trigger for the Next button in the player being set to "Jump to" and "Next slide".
It would be ideal to fix the issue on Firefox because we do not want to confuse our students and lecturers. We recommend Firefox for running Blackboard Collaborate Ultra sessions because there are webcam issues on Chrome using the virtual classroom tool.
Please advise.
Btw, I'm using SL2 licence.
Hi Nijel. I see that Vevette is working on your case for this issue and has asked a follow up questions. Thanks for sending us those steps and details! You can reply to her email.
Feel free to update this discussion with any solutions you discover.
Hi Crystal, thanks for your reply. I've provided the SL2 source file to Vevette. She has been given access to my Blackboard development course. I've tried changing different player and slide settings along with different SCORM Player Behaviour settings in Blackboard Learn. None of these combinations solved the spinning wheel issue. It's frustrating, but I won't let it win.
Hi Nijel,
I checked in on your case this AM and saw you and Vevette were able to isolate the issue to some images in the course that you were looking at removing. I hope that helps, but please feel free to let either of us know if you need more help!
This discussion is closed. You can start a new discussion or contact Articulate Support.