Conditional Navigation in E-Learning #390: Challenge | Recap
“How do I restrict navigation until one or more modules are viewed?”
How do you lock navigation until the learner views all co...
Published 3 years ago
Version 1.0
Blog Post
Hi all, I sort of combined this and last week's challenge. I used two number variables, one to track all the buttons on a slide were clicked and another as part of a self-assessment at the end.
I realize this might look like a satire of new employee orientations and/or jobs but it's not meant that way: https://360.articulate.com/review/content/d1e53763-e726-4eb2-9c62-3801e805dcf8/review
I realize this might look like a satire of new employee orientations and/or jobs but it's not meant that way: https://360.articulate.com/review/content/d1e53763-e726-4eb2-9c62-3801e805dcf8/review
- I didn't understand at the beginning because the sound didn't start until I arrive to the 9 buttons to click ^^' So the animation was a bit strange.
About the variable that you change when we click on a button, I kind of "cheated" and had the self-assessment without visiting all the levels. Instead of "adding 1" to your variable each time that the button is clicked, you should add the condition that the state of the button is "normal" and not changed. So people have to visit each of them and can't go forward by cheating like me :P- I agree, i just don't think there's a way to remove them without removing all the accessibility features. Am I wrong?
- Can you elaborate on what you mean by adding the condition that the button is normal? In what circumstances?
I haven't had issues playing the audio when I did it but this is good to know.- I suppose that right now, you have a "programmation" that is "each time you click this button, add 1 to the variable (i don't know your variable's name) or it is when you enter a layer/slide after clicking a button.
To avoid someone clicking the same button and still managing to arrive to the "assessment part", you keep the "add 1 when you click on a button" but you add on the bottom of this event in the condition "If the state of my button is "normal".
In that way, after visiting a button, you change his look (it becomes darker). So it's not the same state. SO if someone clicks again on the same button, since the state will not be the same, the "add +1 to the variable" event will not trigger.
For the audio, after I arrived to the main menu and clicked on "return" on the player, I heard the audio well.
