During slide transitions, the player takes user input and buffers it - ruining disabled next button feature

Jul 27, 2021

I have made a round trip slide where the learner clicks to solve something on subsequent slides to be returned. It all works well with state control, and I disable the Next button on slide triggers if not all state conditions are met.

However, during transition to this slide from the last sub slide, the Storyline player actually allows the user to click the Next button, and this input buffers so during the small time frame that the transition takes, before triggers are applied.

So you can skip it :(

It would be nice if Storyline Player ignored player inputs during transitions so this didn't happen.

My work around is to remove the next button entirely and make slide navigation dependent on the user clicking a custom made button. But UX wise I really hate to remove the well known fixtures from the player. It messes with the users expectations.

1 Reply
Lauren Connelly

Hello Soren!

Thanks for taking the time to share this with us! I'm interested to see which triggers you're using to change the state of the navigation buttons.  Are you basing the state of the navigation buttons off of when the timeline starts or something else? 

If you'd like to share your .story file, I'm happy to take a look!