Dec 17, 2014
SO I know you can set the navigation to restrict in the player, but his does not work for me.
My screens have interactions that say for example click on the buttons for more information. There is audio to go with this. If you read the text quicker than the audio and click the button, the main timeline does not finish, in which case your 'next' button has not been unlocked, and you are stuck on the screen!
I have seen the work around to leave the navigation as free and then add in code after publishing to lock the menu, but if there are any corrections there after this process needs to be repeated each time (and is easily forgotten). - would be great to still just have the menu lock option.
I also have other courses where the client would like the 'next' button to be locked and so I need to work out a solution to this!