Forum Discussion
Animated path and variable changes
I'm happy to take on the challenge đ, LeonardSaucierâ . A small modified .story file is worth a thousand words, but basically, here's what I did.
-Since all the âbtn-continue 1â buttons have the same name and appearance on all layers (which is confusing), I took the liberty of coloring the one on the base layer red (the one youâre trying to make ânormalâ) and renaming it, to help me create a trigger later.
-You donât need the Showcontinue variable; you already have the Slider1 variable.
-To prevent the video from reappearing/disappearing on every layer, use this trick: click the small triangle below the list of objects on the layer, and uncheck the eye icon next to the video: This element will not be visible when the âFeet-Weight-Applicationsâ layers appear. Do this on every layer except on the first one because you need your âquick exitâ animation once. Look at the attached image: itâs in French, sorry, but youâll recognize your file.
-Finally, on the last âApplicationsâ layer, simply create a trigger: âChange the state of âBtn Continue on the base layerâ to Normal when the learner clicks on âbtn-Continue 1â.â Place this trigger before the trigger that closes this layer, just to be safe.
All done.
Andrew is right. We should do something to prevent the learner from dragging the slider too quickly to the top of the scale.
Hi Leonard. I like your style, this was a fun and funny course. I was able to get some fixes, but with some caveats.
The video hang-up seems to me to relate to it occupying the entire timeline. I removed the motion path and replaced it with an Exit Animation, and then dragged the end of the video on the timeline to a little after where the video finishes. I've experienced issues both with animation paths in general as well as with videos stretched to fill the entire timeline. Since the video is still technically "visible" on the timeline even after your motion path has removed its visibility to the learner, I've found Storyline tends to still try and act on/with it. Maybe the animation path settings are related, but strangely I wasn't able to see the actual animation path on the Animations tab. Regardless, exiting the video ensured it was well and truly out of the picture for every subsequent return to the base layer.
I was able to get your final Continue button to show, but weirdly I'm not quite sure how since I was trying a number of different things. Your showContinue variable is making it to 10 but the Set state trigger on the base layer doesn't seem to be reacting the way we think it should. Again, I was able to get it to trigger in my edited file, but after comparing it to yours, I don't visually see a difference. I expect a workaround might be to have the Applications layer's Continue button simply progress learners to the next slide rather than return to the base layer only to show a second Continue button.
I was also able to break your course while experimenting. Your layers adding values to showContinue is novel but can produce situations where showContinue becomes greater than 10 since each time I click a layer's Continue, its value is added to the variable once again. Since I can revisit layers, the addition to the variable can happen more than once. A bulletproof trigger might check the value of showContinue is >= 10 to account for revisits; however, I was also able to move the character multiple spaces up the ladder if I moved my mouse quickly, skipping layers. This would naturally allow someone to make it to the top with a showContinue less than 10.