Usually we control the Storyline player 'Next - Previous' button functionality using triggers, but still it is in clickable state. Is there any option to disable the player 'Next' button visually also?
Yes, in Story view, select the slide for which you want to hide the buttons, then uncheck "Prev" and "Next" textboxes under Slide navigation controls (bottom right).
Thanks for the reply. However, I don't want to remove the player 'Next' button from player. The functionality is, 'Next' button should be disabled until the slide audio completes, and I have handled this with the help of trigger. That means I have successfully disabled the button functionality, but I also want the 'Next" button appearance in disabled state as well, until the slide audio completes. Is there any way to handle the state of player Next button?
Whilst you can disable the functionality of a built-in player control by using variables or the states of other objects, you can't apply a visual 'disabled' state unfortunately.
No, there isn't a way to control states of stock "Prev-Next" Player buttons AFAIK.
However, there's a workaround and an alternative :
a) If you can do without the seekbar, create your own custom navigation onslide, replace the stock buttons and create your disabled states as you see fit, OR
b) Hide the Next-Prev buttons as above. Change the slide to "slide advances automatically". Duplicate your slide. Notice the end state of your slide elements and make the copied slide reflect those states. Check the Next-Prev buttons on that 2nd slide and switch back to "slide advances by user".
The requirement is specifically related to making the state disabled of Player Next button. Anyways, thanks for the alternative suggestions. Let me know if you figure out some solution to achieve this requirement.
Yes, I have suggested the same thing for this issue. However, the requirement is to keep the Next and Previous button in player only. so in this case, adding custom buttons on the screen internally, cannot help. :(
7 Replies
Yes, in Story view, select the slide for which you want to hide the buttons, then uncheck "Prev" and "Next" textboxes under Slide navigation controls (bottom right).
Hope this helps,
Alex
Hi Alex,
Thanks for the reply. However, I don't want to remove the player 'Next' button from player. The functionality is, 'Next' button should be disabled until the slide audio completes, and I have handled this with the help of trigger. That means I have successfully disabled the button functionality, but I also want the 'Next" button appearance in disabled state as well, until the slide audio completes. Is there any way to handle the state of player Next button?
Regards,
Sayali S.
Hi Sayali - welcome to Heroes!
Whilst you can disable the functionality of a built-in player control by using variables or the states of other objects, you can't apply a visual 'disabled' state unfortunately.
It would be a great feature request though!
Antony
No, there isn't a way to control states of stock "Prev-Next" Player buttons AFAIK.
However, there's a workaround and an alternative :
a) If you can do without the seekbar, create your own custom navigation onslide, replace the stock buttons and create your disabled states as you see fit, OR
b) Hide the Next-Prev buttons as above. Change the slide to "slide advances automatically". Duplicate your slide. Notice the end state of your slide elements and make the copied slide reflect those states. Check the Next-Prev buttons on that 2nd slide and switch back to "slide advances by user".
Hey Alex,
The requirement is specifically related to making the state disabled of Player Next button. Anyways, thanks for the alternative suggestions. Let me know if you figure out some solution to achieve this requirement.
Thanks,
Sayali S.
Hey Sayali!
I would like to add that u can remove the built in button n add a custom next button, so, u may change it to any state u desire.
Hi Hassan,
Yes, I have suggested the same thing for this issue. However, the requirement is to keep the Next and Previous button in player only. so in this case, adding custom buttons on the screen internally, cannot help. :(
This discussion is closed. You can start a new discussion or contact Articulate Support.