I am having issues with my next buttons working in Storyline 2. Sometimes you have to hit the next button 6+ times for the slide to advance even if there are no variables or conditions. Please help.
Hey Wendy - is this true! Are you talking about locked Nav? It does not make sense to tie the next button to the timeline - Users should be able to click Next at any time to advance.
I am having issues with the previous button being unresponsive on the first couple of clicks in some instances.
I'm sure that is what I read about the next button and timeline in SL2 so I have always made sure that my timeline length is short unless objects are triggering interactions that the user has to complete before moving on.
Re your Prev button issue...I have been editing some .story files for a client and also couldn't work out why I had to press in a specific place on the Prev/Next (these were custom buttons) to progress and it was an arrow image they had overlaid over the top of the buttons that almost covered the entire Prev/Next button images except for a small corner...
Hi Denise, Please check to see if your navigation is restricted or free. If it is restricted, the next button is not active until the timeline ends. You can find this setting in the player by clicking on the gear icon. Cheers, Julie
p.s. Wendy, You are the one that told me about the changed navigation logic in SL2. From your advice, when I have to use the restricted menu, I change the frame.xml so that the restricted in SL2 works like the restricted navigation in SL1.
The next button won't advance to the next slide until the end of the timeline has been reached if you're using Locked or Restricted navigation. This was a change from the behavior of SL1 where the player navigation method and the slide next/prev buttons operated independently.
If the previous button is not working at all, that sounds like something that we'd need to see and take a look at.
Thanks everyone! I have shortened my timelines per slide to 1 second each so that the user can advance to the next slide. I have it set to restricted because I want them to go thru all the slides on their required compliance courses. Thanks everyone! I thought I was going crazy for just a day! :) Have a great week :)
We incorporate audio into our courses, which generates about a 30-45 second time line.
We need to use "restricted" in our menu settings to prevent a student from jumping around in a module, but I would still like them to have the freedom (like they did in Storyline 1) to skip ahead even though the timeline is not finished. What can we do for a student, who reads faster than our audio, if she or he wants to skip though slides?
Basically, I would like to un-tether the "next" button to the timeline. Is that possible? And if not, could it be changed in the next Storyline 2 Update?
Sorry to bring up an old thread but for some reason a specific slide within my content will not let the user proceed to the next slide even when the TL reaches the end.
Users are allowed to drag it but should only be able to hit next button once the timeline has reached the end.
The trigger for the next button is still active.
FYI - the slide uses 2 layers. not sure if this would be contributing to the problem
I can see what's happening but not sure why. I created a new file and imported the first four slides in. Then i copied the content from slide 1.3 layer onto the base, and the content from the base onto a layer. I set triggers to play the layer when timeline starts, then hide the layer when timeline ends and play the rest of the content. It appears to work fine now when clicking on the Next button.
Hope this workaround helps in the short term - you may want to submit a support case with Articulate. I have seen this issue posted before but haven't seen the solution.
I was playing around in your file too - and had shortened the layer timeline to match the audio I thought was playing through all that layer and then set it to hide the slide layer when the timeline finished. That allowed me to advance - so similar to what Wendy suggested with switching the base and layer elements.
It seems that the function of the next button is getting caught up in the slide layer (based on setting to hide all the items in the base layer and that the layer remains visible). I haven't seen this before though, so I'm going to open a case on your behalf to get some more eyes on the behavior.
Thanks for investigating and finding a work around! I can't seem to download the file you uploaded. When i click on it I am taken to a page that displays XML code, not an ASL file.
Hi Michael! Can you try to open this link in a different browser and download? The link that Wendy shared above seems to work just fine for me. Let us know how that goes :)
I have a similar problem with the next and previous buttons not working. Due to the deadline, I have to delete some slides, copy the contents using the slides which are 'more stable', adjust timeline and opted for the built-in next and previous buttons on the player.
This thread is a bit dated, but I am sorry to hear that you had trouble with your previous and next buttons.
It sounds like it's not an issue you are dealing with right now, but if you get back to building a similar project and run into issues again, be sure to reach out so that we can take a look and help you out :)
I literally spent hours trawling through all the other explanations, trying things like changing the state of the Next button on condition of blah, blah, blah. Then I found your oh so simple solution and it worked! Muchisimas gracias Julie - you are a champion.
28 Replies
Hi Denise
SL2 next button behaviour works on the length of the timeline
I'm sorry I am not sure what that means? I need my users to be able to hit the next button to move forward, not wait for the timeline to end.
Thanks,
Denise Granger
I understand - so you need to make your timeline only a few seconds long so that can happen and have slide properties set to advance by user
Hey Wendy - is this true! Are you talking about locked Nav? It does not make sense to tie the next button to the timeline - Users should be able to click Next at any time to advance.
I am having issues with the previous button being unresponsive on the first couple of clicks in some instances.
Hi Nancy
I'm sure that is what I read about the next button and timeline in SL2 so I have always made sure that my timeline length is short unless objects are triggering interactions that the user has to complete before moving on.
Re your Prev button issue...I have been editing some .story files for a client and also couldn't work out why I had to press in a specific place on the Prev/Next (these were custom buttons) to progress and it was an arrow image they had overlaid over the top of the buttons that almost covered the entire Prev/Next button images except for a small corner...
Hi Denise, Please check to see if your navigation is restricted or free. If it is restricted, the next button is not active until the timeline ends. You can find this setting in the player by clicking on the gear icon. Cheers, Julie
p.s. Wendy, You are the one that told me about the changed navigation logic in SL2. From your advice, when I have to use the restricted menu, I change the frame.xml so that the restricted in SL2 works like the restricted navigation in SL1.
I'm just using the default player buttons in this case (yes, guilty as charged).
As for the logic on the Next button, I'm going to see if I can find more info because I thought that only applied to locked Nav - but what do I know.
Hi all,
The next button won't advance to the next slide until the end of the timeline has been reached if you're using Locked or Restricted navigation. This was a change from the behavior of SL1 where the player navigation method and the slide next/prev buttons operated independently.
If the previous button is not working at all, that sounds like something that we'd need to see and take a look at.
Thanks everyone! I have shortened my timelines per slide to 1 second each so that the user can advance to the next slide. I have it set to restricted because I want them to go thru all the slides on their required compliance courses. Thanks everyone! I thought I was going crazy for just a day! :) Have a great week :)
Awesome - happy to hear it Denise and I hope you have a great week as well!
Hi Ashley, thought I should let you know that the prev button works fine. The triggers somehow got deleted on a couple of the slides.
Thanks Nancy for the update and I'm glad it was something simple!
We incorporate audio into our courses, which generates about a 30-45 second time line.
We need to use "restricted" in our menu settings to prevent a student from jumping around in a module, but I would still like them to have the freedom (like they did in Storyline 1) to skip ahead even though the timeline is not finished. What can we do for a student, who reads faster than our audio, if she or he wants to skip though slides?
Basically, I would like to un-tether the "next" button to the timeline. Is that possible? And if not, could it be changed in the next Storyline 2 Update?
Hi Benjamin,
I just answered a similar question in this thread and linked to an example that should help you.
Hello,
Sorry to bring up an old thread but for some reason a specific slide within my content will not let the user proceed to the next slide even when the TL reaches the end.
Users are allowed to drag it but should only be able to hit next button once the timeline has reached the end.
The trigger for the next button is still active.
FYI - the slide uses 2 layers. not sure if this would be contributing to the problem
Any ideas?
Thanks
Michael.
Hi Michael
can you share the slide with the issue and the following slide - easier for someone to help if they can see your file setup.
Hi Wendy,
Thanks for you prompt reply. I've attached our ASL file. The issue is with the 3rd slide.
I think i replied to another thread regarding an issue with layers (same slide), although i appear to them working (sort of).
Thanks
Michael.
Hi Michael
I can see what's happening but not sure why. I created a new file and imported the first four slides in. Then i copied the content from slide 1.3 layer onto the base, and the content from the base onto a layer. I set triggers to play the layer when timeline starts, then hide the layer when timeline ends and play the rest of the content. It appears to work fine now when clicking on the Next button.
Hope this workaround helps in the short term - you may want to submit a support case with Articulate. I have seen this issue posted before but haven't seen the solution.
Sorry I can't be more help.
Hi Michael,
I was playing around in your file too - and had shortened the layer timeline to match the audio I thought was playing through all that layer and then set it to hide the slide layer when the timeline finished. That allowed me to advance - so similar to what Wendy suggested with switching the base and layer elements.
It seems that the function of the next button is getting caught up in the slide layer (based on setting to hide all the items in the base layer and that the layer remains visible). I haven't seen this before though, so I'm going to open a case on your behalf to get some more eyes on the behavior.
Keep an eye out for an email from Support!
Hi Wendy,
Thanks for investigating and finding a work around! I can't seem to download the file you uploaded. When i click on it I am taken to a page that displays XML code, not an ASL file.
Thanks
Michael.
Hi Michael! Can you try to open this link in a different browser and download? The link that Wendy shared above seems to work just fine for me. Let us know how that goes :)
Thanks everyone for your help and the interim fix!
Apologies for the delay in responding I've been travelling with work.
Thanks again :)
I have a similar problem with the next and previous buttons not working. Due to the deadline, I have to delete some slides, copy the contents using the slides which are 'more stable', adjust timeline and opted for the built-in next and previous buttons on the player.
Hi Suzi,
This thread is a bit dated, but I am sorry to hear that you had trouble with your previous and next buttons.
It sounds like it's not an issue you are dealing with right now, but if you get back to building a similar project and run into issues again, be sure to reach out so that we can take a look and help you out :)
I literally spent hours trawling through all the other explanations, trying things like changing the state of the Next button on condition of blah, blah, blah. Then I found your oh so simple solution and it worked! Muchisimas gracias Julie - you are a champion.
This discussion is closed. You can start a new discussion or contact Articulate Support.