I have found some rather old discussions (8 yrs) about people requesting the ability to turn the Menu ON and OFF from a button in the slide, but I believe this still isn't possible if the Menus & Controls are turned OFF, correct? I don't want that big grey bar unnecessarily taking up screen real-estate.
So, my next option is to build my own Menu, which I've done via a layer on my master slide. My next challenge is how to restrict people from jumping ahead if they click anywhere in the menu (including the last slide). Can I easily achieve the same thing as what the Menu: Restricted option does in the Player settings? If not, I'll have to do away with the Menu altogether :(
So it looks like I'm going to have to do the following, yes?
create a variable for each slide that I want to include in the menu (there may be 30 or more)
set up a trigger to change the variable when the user visits the slide
set triggers for the hyperlinks in the menu to test the destination page's variable and if it hasn't been visited, load a message (perhaps on a layer) that states they can't go there yet because they are not allowed to jump ahead.
That's gunna be a LOT of wiring to get it to work right. I was hoping to avoid such a beast!
It's such a shame we can't just hide/show Storyline's menu without having to turn the Menu bar ON in the player. I've come from developing in Captivate and this is exactly what you can do there. You can have the Menu appear as a tiny icon at the top left of each slide and you can either press the icon or create a button, yourself, that shows it (floats over the top of your content) and hides it - very easy - and it takes advantage of the built-in menu functions.
In general, yes, but philosophically, I have trouble with this:
set triggers for the hyperlinks in the menu to test the destination page's variable and if it hasn't been visited, load a message (perhaps on a layer) that states they can't go there yet because they are not allowed to jump ahead.
I am strongly frustrated by being able to see things to click on that do nothing. Consequently, I avoid creating them.
But it isn't as much work as it seems. If you put the menu on the master, you may have to do it only once.
3 Replies
There is a sample of a custom menu that restricts navigation here: n
https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers
You should be able to apply the principles in the restricted or mixed navigation (or a combination) to your menu.
Thanks for your help Walt (great sample BTW)!
So it looks like I'm going to have to do the following, yes?
That's gunna be a LOT of wiring to get it to work right. I was hoping to avoid such a beast!
It's such a shame we can't just hide/show Storyline's menu without having to turn the Menu bar ON in the player. I've come from developing in Captivate and this is exactly what you can do there. You can have the Menu appear as a tiny icon at the top left of each slide and you can either press the icon or create a button, yourself, that shows it (floats over the top of your content) and hides it - very easy - and it takes advantage of the built-in menu functions.
Many thanks!
Brett
In general, yes, but philosophically, I have trouble with this:
set triggers for the hyperlinks in the menu to test the destination page's variable and if it hasn't been visited, load a message (perhaps on a layer) that states they can't go there yet because they are not allowed to jump ahead.
I am strongly frustrated by being able to see things to click on that do nothing. Consequently, I avoid creating them.
But it isn't as much work as it seems. If you put the menu on the master, you may have to do it only once.