Disabling Next button until users finish interacting with slide

Hi everyone,

I followed the following instructions on how to disable the next button until the use finishes interacting with a slide.

Has anyone noticed that when the Next button is enabled you can click it very quickly and repeatedly to skip several pages? There seems to be a small delay between the loading of a page and the actually triggering of the on Timeline Start event (which disables the next button). Within this tiny time gap the user can skip pages by clicking the next button quickly. Can anyone replicate this?

Any idea on how to prevent this from happening? I'm using custom Back/Next buttons by the way.

Thank you.

6 Replies
Ashley Terwilliger

Hi Kallidus,

I haven't seen that, but you mentioned a trigger to change the "next" button on the Timeline start - I would suggest to check your trigger order as well. Items are triggered or deployed from top to bottom. If you think it's something that our team should review, please feel free to share your .story file with us here. If you'd prefer to share privately you can also send it along here. 

Ashley Terwilliger

Hi Kallidus,

I'm just following up again to be sure you're receiving Jonathon's emails - he sent another one on November 11 which I've copied below:

I replied to your email last Nov. 2, Friday, but it seems that you were not able to receive it. 

Anyway, I just informed you that I was able to reproduce the issue in your file. 

I did a couple more test and see if I would be able to reproduce the issue in a new file following the instructions from this article: 
http://www.articulate.com/support/storyline/how-to-disable-the-next-button-until-users-finish-interacting-with-a-slide 

Unfortunately, I was not able to reproduce the issue. (he shared a link to the test file in his email). 

One thing I noticed is that my NEXT button starts in hidden state as suggested from the article. This is a good way of preventing the user from accidentally clicking it since they start hidden as they load. 

In your project, they are not. This could be where the issue is coming from so you might want to recheck your triggers again. The triggers could be skipped as the user clicks on the buttons rapidly.