I am working on this module and want a car to follow a path on a road as the learner moves on to each Step. I put the car within the Normal state so when the learner gets to that Step, it shows the car and the Normal State of that button. However, the car I added to the Normal State is not showing up when I click through.
Thank you Michael, that was super simple and wish I had thought of that first.
However, since I made that change, now I can see the car at all the Steps at the same time. The car is attached to the Normal state, which changes for my Chevrons, but the Car shows up all the time. Even with Steps 2-5 initial state being set to Disabled.
The Built in states, like Hover, Disabled, Visited, and Selected build on Normal (and, in fact report themselves to be equal to Normal), so the Normal shows through the Disabled state.
When I duplicated Disabled, named it No Car, and set the initial state to No Car, the car disappeared.
But a bigger problem is this trigger:
The only to get the timeline to start every time you revisit the menu slide is to set the slide to reset to initial condition on revisit. But if you do that, then the buttons are all reset to their initial state, and forget that they were visited.
What you have to do is to use a variable, rather than a state to remember which steps have been visited.
This was extremely helpful! I went in and messed around with the variables and I think I got it mostly there. Your example file was amazingly helpful!
However, I am still having trouble with the Normal State showing up incorrectly when only the first Normal State is showing up (Step 2 normal state is showing up when I only want step 1 to show up), and not showing the Visited State. (I feel like I have too many triggers, but so lost as to what to remove.) Do i need to create a new state for Visited that wouldn't be attached to normal, like you did for the "No Car" State?
Once the trigger to jump to 1.3 begins to be executed, all the rest of the Button triggers are ignored, and don't happen. So the value of the variable is never changed. Move "Jump to" down the list until it is the last trigger executed.
Also, set the Menu slide to "Reset to initial state" when Revisiting, to ensure that the timeline starts every time.
Then when it starts, and the variable is True, change the state not to Normal, but to No Car. Don't use Visited, because creating a trigger to change to Visited can conflict with the built-in triggers that all the built-in states have.
6 Replies
On slide 1.3, try moving the Road.png bitmap to the bottom of your timeline.
Thank you Michael, that was super simple and wish I had thought of that first.
However, since I made that change, now I can see the car at all the Steps at the same time. The car is attached to the Normal state, which changes for my Chevrons, but the Car shows up all the time. Even with Steps 2-5 initial state being set to Disabled.
Am I missing something super simple again?
The Built in states, like Hover, Disabled, Visited, and Selected build on Normal (and, in fact report themselves to be equal to Normal), so the Normal shows through the Disabled state.
When I duplicated Disabled, named it No Car, and set the initial state to No Car, the car disappeared.
But a bigger problem is this trigger:
The only to get the timeline to start every time you revisit the menu slide is to set the slide to reset to initial condition on revisit. But if you do that, then the buttons are all reset to their initial state, and forget that they were visited.
What you have to do is to use a variable, rather than a state to remember which steps have been visited.
You can see how to do that by looking at the sample attached to this discussion: https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers
You want the restricted navigation.
Hi Walt-
This was extremely helpful! I went in and messed around with the variables and I think I got it mostly there. Your example file was amazingly helpful!
However, I am still having trouble with the Normal State showing up incorrectly when only the first Normal State is showing up (Step 2 normal state is showing up when I only want step 1 to show up), and not showing the Visited State. (I feel like I have too many triggers, but so lost as to what to remove.) Do i need to create a new state for Visited that wouldn't be attached to normal, like you did for the "No Car" State?
Thanks for your help!
Try changing the order of these two triggers:
Once the trigger to jump to 1.3 begins to be executed, all the rest of the Button triggers are ignored, and don't happen. So the value of the variable is never changed. Move "Jump to" down the list until it is the last trigger executed.
Also, set the Menu slide to "Reset to initial state" when Revisiting, to ensure that the timeline starts every time.
Then when it starts, and the variable is True, change the state not to Normal, but to No Car. Don't use Visited, because creating a trigger to change to Visited can conflict with the built-in triggers that all the built-in states have.
Walt! Amazing! Thank you so much, I now have a module that is behaving as I am hoping it would. Your insight and guidance is greatly appreciated!
This discussion is closed. You can start a new discussion or contact Articulate Support.