Removing or Hiding the Previous/Next Buttons?

Jun 27, 2012

Hi There! I'm using Storyline to put together a (really cool) museum-style interaction that will play on a touch screen computer at a historical site! I'd like to essentially make the interaction play full screen at 1280X720, so I've gone in and set all of the player elements as transparent.  Here's my question: I have gotten rid of everything but the previous and next buttons- how do I turn these off?

Thanks!

110 Replies
Leslie McKerchie

Thanks Eileen!

It is the expected behavior for them to be present during quiz review:

When learners review a quiz (or revisit question slides they've already submitted), they'll see Articulate Storyline's built-in Prev and Next buttons in the lower right corner of the player—even if you've disabled them throughout your course. These navigation buttons are necessary for learners to review quiz slides.

You are welcome to share your thoughts with our product development team here if you'd like to see this handled differently in the future.
Irene Lee Ranstorp

Hi,

I have created custom buttons for prev/next/submit and a quiz. On every slide (and in player settings), I have disabled default next/prev/submeit, When revisiting= Reset to initial state, player features = player defaults. However, the default next/prev buttons still turn up. I have not ticked of revisit quiz nor review quiz.

Is there anything else, I can do?

Thanks.

Best regards,

Irene

Ashley Terwilliger-Pollard

Hi Irene,

When learners review a quiz (or revisit question slides they've already submitted), they'll see Articulate Storyline's built-in Prev and Next buttons in the lower right corner of the player—even if you've disabled them throughout your course. These navigation buttons are necessary for learners to review quiz slides.

If you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know. We value your feedback. 

I know a few users have mentioned that removing all the player features would allow them to not see those buttons as then there is no place for them to appear. This would involve not using elements such as the seekbar, volume, etc. so I'm not sure that's a solution for you. 

If you're still struggling with this set up and you'd like the community to take a look you're welcome to share your .story file here with us. You can post it using the "Add Attachment" button at the bottom of the reply box. 

Ashley Terwilliger-Pollard

Hi Doug,

I'm sorry that this behavior is causing difficulty for you and as I mentioned earlier, it's the expected behavior based on how Storyline currently operates and is providing a way for the users to navigate the slides. Hopefully Sam's method will work for you and you can also always share your thoughts in regards to this behavior by submitting a feature request to change it. 

Kevin Fortier

I am surprised to see how old this solution is, however it is still valid.  I am new to using StoryLine as I used another product for a few years. This was a very simple change to do globally for the other tool and I found myself spending a lot of wasted time within the Player Properties to which I would expect this option to be found.  As always the Articulate Community has helped me find a solution and I hope that a very simple solution can be added into the tool for the next release.  Thanks!

Ashley Terwilliger-Pollard

Hi Joe,

You may want to test this in a few different environments as it may be the load time of your server/LMS or overall connection that is causing them to be visible for a brief moment before disappearing. There isn't a way to stop them altogether though as they'll reappear as a part of the review functionality. 

Ashley Terwilliger-Pollard

Hi Joe,

Are you publishing for CD or another local spot or just testing the published output locally? If the latter, I'd recommend uploading it to the intended environment to properly test. 

I do know that a number of users mentioned removing all elements of the player to ensure that the next/prev buttons had no space to show up - but I can't guarantee that'll always work. You can view the directions here on how to remove the player elements.