I am at my wits end. My next buttons don't work. When revisiting a slide they are fine, but at first visit to the slide the user can't advance until the timeline is finished. I have created a few lessons in SL1 and never had this problem. The slide properties are set and the trigger "jump the next slide when user clicks next button" are consistent. Help.
I'm attaching one of my scenes, too big a file to send my whole file.
The next trigger in Storyline 2 is dependent on the slide timeline if you've enabled restricted or locked navigation for your player menu. This was a change in Storyline 2 based on feedback we heard from users in Storyline 1, and if you'd prefer to see a different behavior you're want to share your thoughts in the form of a feature request here.
It appears to be. I changed the navigation to free and it is working correctly in your attached file. I usually add my own next/back button for more control so I had not had that issue previously. Tricia
I'm glad you were able to find that answer, and this is a difference in behavior from SL1 to SL2 in that the player navigation methods now control the player next/prev buttons as well.
I filled out a feature request. I'm hoping Articulate will switch this feature back. I don't want to have to create custom next buttons due to real estate. Having the user skip ahead 5 slides is not wanted, but forcing them to the end of any slide is not ideal either. For now I've left it as free but I am hoping this is temporary until the next version of Storyline comes out. I hope they fix this.
Sorry to hear that and if you haven't already you're welcome to submit a feature request as well here. The original change was made based on user feedback in regards to wanting the menu navigation and player navigation work together so that they didn't have to set up individual elements.
7 Replies
IS THIS THE ANSWER:
Ashley TerwilligerHi Natasha,
The next trigger in Storyline 2 is dependent on the slide timeline if you've enabled restricted or locked navigation for your player menu. This was a change in Storyline 2 based on feedback we heard from users in Storyline 1, and if you'd prefer to see a different behavior you're want to share your thoughts in the form of a feature request here.
It appears to be. I changed the navigation to free and it is working correctly in your attached file. I usually add my own next/back button for more control so I had not had that issue previously. Tricia
Hi Vanesssa,
I'm glad you were able to find that answer, and this is a difference in behavior from SL1 to SL2 in that the player navigation methods now control the player next/prev buttons as well.
Hi Ashley,
I filled out a feature request. I'm hoping Articulate will switch this feature back. I don't want to have to create custom next buttons due to real estate. Having the user skip ahead 5 slides is not wanted, but forcing them to the end of any slide is not ideal either. For now I've left it as free but I am hoping this is temporary until the next version of Storyline comes out. I hope they fix this.
Vanessa
There are a few workarounds for this behavior that don't involve custom buttons, such as the one here.
Agreed. Very unhappy with this change. : (
Hi Jacqueline,
Sorry to hear that and if you haven't already you're welcome to submit a feature request as well here. The original change was made based on user feedback in regards to wanting the menu navigation and player navigation work together so that they didn't have to set up individual elements.
This discussion is closed. You can start a new discussion or contact Articulate Support.