In the final portion of our hands-on Advanced Storyline 360 training, we end the session with some fun, easy, and favorite features of mine: sliders and dials! During this segment, we task the students with creating a fairly simple interaction that we use often: showing a timeline of events. In that exercise, the slider has eight stops, and the stops are equal distance apart. When teaching this, however, we’re often asked, “What if I need my slider to stop at points that aren’t equal distance apart?” While there are varying
UPDATE! As of October 2019, the Storyline 360 trigger wizard was updated to use the same intuitive language as the triggers panel so it’s consistent and understandable. For 360 users, “Assignment and Not Assignment” have been replaced with “Set and Toggle.” The language is different, but the steps listed below still work. Learn more about the new trigger workflow here, and then read on! Although not used as often, the “=NotAssignment” (also known as “toggle”) variable/trigger can be a great way to help you create engaging interactions for your learners!
In a recent custom virtual training, a student asked for help in creating scenario-based courses in Storyline. When the scenario arrived to a point where the learner received a quiz question, they wanted the learner to not only be able to review content they had already seen, but to also highlight important information. The main consideration here was that they did not want the information highlighted on the original slide, only when being reviewed. While there are several ways one might accomplish this, one of the easiest ways is to
This question was sent to me just this month after a training session. Let me set it up for you… In our advanced class, we teach the students how to build a custom menu and control the navigation of that menu using True/False Variables (aka, Boolean–for the nerds out there). You can view a simplified version of the course here. You can also download that .story file at this link. What is happening in this example is the “visited” states of the buttons are designed to look like an “in
There’s one moment in particular that brings me extra delight as an instructor during our Storyline workshops. It’s that look of awe from participants when we draw attention to a trigger that works because of the sequential order of the triggers themselves. As you may know, triggers execute all of the action in our Storyline builds. Aside from a few timeline-based events, we see most of our slide actions listed in the Triggers Panel. However, the sequential order of triggers within the panel can also be significant. You may or