I need help to create a menu that has disabled sailing on a first visit, but on the second visit, the student can go to the content they want. Is this possible?
Yes this is very much possible, you will need to create a variable. This will keep track of the pages that the end user has visited.
If you create a variable called 'pages' you can add a trigger to add 1 to your newly created variable only when the user clicks Next. So for example, on page one when the user clicks next this will add 1 to the 'pages' variable this will equal to the pages viewed. By doing this, you know the user has completed that page and has moved on. Therefore the page as been fully viewed.
To control the locking, you add another trigger to say Change state of (next button) to (Hidden) when timeline starts, IF (pages) variable is less than (what ever number you assign that page e.g 1) So when a user accesses that page it will run that trigger. If the variable is less than the number you assigned the page it will keep the next button hidden otherwise it will leave it visible for the user to click through.
Same principle for the menu.
Hope I've made it clear, I said to myself "Yes this will be easier to explain" until I actually started to jot an answer down.
If you're using the built in menu of Storyline you can look at using the restricted menu setting that stops the user from skipping around on slides, but once they've visited a slide they'd be able to revisit it from the menu. You can read more about how to set this up here.
5 Replies
Hi Toni,
Yes this is very much possible, you will need to create a variable. This will keep track of the pages that the end user has visited.
If you create a variable called 'pages' you can add a trigger to add 1 to your newly created variable only when the user clicks Next. So for example, on page one when the user clicks next this will add 1 to the 'pages' variable this will equal to the pages viewed. By doing this, you know the user has completed that page and has moved on. Therefore the page as been fully viewed.
To control the locking, you add another trigger to say Change state of (next button) to (Hidden) when timeline starts, IF (pages) variable is less than (what ever number you assign that page e.g 1) So when a user accesses that page it will run that trigger. If the variable is less than the number you assigned the page it will keep the next button hidden otherwise it will leave it visible for the user to click through.
Same principle for the menu.
Hope I've made it clear, I said to myself "Yes this will be easier to explain" until I actually started to jot an answer down.
Regards
Stephen.
Hi Toni,
If you're using the built in menu of Storyline you can look at using the restricted menu setting that stops the user from skipping around on slides, but once they've visited a slide they'd be able to revisit it from the menu. You can read more about how to set this up here.
Or that, but my solution is for custom players. which enhances user experience as the built in functions look terrible.
Stephen and Ashley,
Thank you very much for your answers, now I'm traveling and I can not prove it. When I got to my office I'll try and I will discuss the outcome.
Regards,
Toni López
No problem Toni - keep us posted whenever you're able to take a look.
This discussion is closed. You can start a new discussion or contact Articulate Support.