Blog Post
Jonathan_Hill
Super Hero
Hello!
Not a fan of locked navigation unless it's absolutely necessary -- but I frequently use 'bookmarking' to track the learner's progress within custom navigation menus. I recently built this short demo to illustrate this principle to my team.
You can visit each room in alphabetical order using the next button, or visit the rooms in any order you choose. When you return to the menu, the doors to the rooms you have already visited remain open. But you can't 'move on' (reset) until all three rooms have been visited.
Demo: https://bit.ly/elhc390
Download: https://bit.ly/elhc390dl
Discussion: https://twitter.com/DevByPowerPoint/status/1551883713469972480
Not a fan of locked navigation unless it's absolutely necessary -- but I frequently use 'bookmarking' to track the learner's progress within custom navigation menus. I recently built this short demo to illustrate this principle to my team.
You can visit each room in alphabetical order using the next button, or visit the rooms in any order you choose. When you return to the menu, the doors to the rooms you have already visited remain open. But you can't 'move on' (reset) until all three rooms have been visited.
Demo: https://bit.ly/elhc390
Download: https://bit.ly/elhc390dl
Discussion: https://twitter.com/DevByPowerPoint/status/1551883713469972480
BriceMaret-a1ab
2 years agoCommunity Member
I like the visual and the simple example.
I'm less convinced with the use of variables, instead of using "visited" states to have the same results (but that was the challenge, I know). The code is quite long but for someone who doesn't like variables, it can be changed into "visited state" and can work nicely.
I particulary appreciate the implementation of the "next" button logic, to let the choice to the viewer.
I'm less convinced with the use of variables, instead of using "visited" states to have the same results (but that was the challenge, I know). The code is quite long but for someone who doesn't like variables, it can be changed into "visited state" and can work nicely.
I particulary appreciate the implementation of the "next" button logic, to let the choice to the viewer.
- Jonathan_Hill2 years agoSuper HeroI'm pleased you picked up on that Brice -- the reason I didn't use a conventional visited state on the doors, is that I reset the menu slide to initial state each time it is visited, so that the character animation repeats - like he's re-entering the scene.
The visited states only hold if the slide is set to resume saved state, which also meant the character was still in the foreground.
The coding is mostly to preserve the animation effect. But yeah, as with all things Storyline there's often more than one way to do something like this.- BriceMaret-a1ab2 years agoCommunity MemberAh that was the reason, to make the character "appear" in front of each door.
As I imagined it, the character was part of a state of each door (to avoid changing the state of the door AND the character). I understand better now ;) thanks- Jonathan_Hill2 years agoSuper HeroI like using variables to change/maintain the appearance of certain elements when the design requires the slide to 'reset to initial state'.
It's not really been highlighted here yet, but visited states only work if you set the slide revisit settings to 'automatically decide' or 'resume save state'.
But sometimes these settings can mean other animations no longer fire, which is where these variables come in handy.