Timelines,triggers and variables

Ok this is less of a challenge but more points of clarification.

1. I created a template from an older course so that I could use the glossary that was in the older course.When I copied my slides into the template & then saved as a new module.All good so far BUT I then found that when the trigger to change the state of the next button to normal happened I could not go to the next slide,I posted a question & a reply stated that I need to have navigation at Free as it was "restricted" all ok now but I then found that delegates can go to the drop down menu in the player & advance to any slide they want.Now in  most of my slides the time line was about 3 mins long as photos dropped off the slide once the timeline for that photo was reached,the problem was that then the next button would work once the 3 mins had completed.So I changed the timeline length to about 20 secs & now that the navigation is restricted the photos will stay on the slide for well over the 20 sec time line & the next button follows the trigger so it all works now I suppose the question I am asking is "why"!

2.My next point is about variables,I watched the videos but I am often confused as to why I need a variable when a simple trigger will do.In the attached there is a screen shot of a slide that I did not create but have on my PC.You will see that there is a trigger to set the next button to normal at when the timeline ends but there is a further trigger to set the slide equal to true when the timeline ends,so here again my question is why do I need to set a variable if the timeline ending triggers the state of the next button?

I realise that this for many of you is the norm but I feel I have missed something with variable sthat others understand.

Many thanks

6 Replies
Walt Hamilton

2. One of the major uses of variables is in conditions of triggers: Perform this action only if this condition has been met. This variable is set so the program can tell if the user has already seen this slide. If this is the second time for the user to view this slide (i.e. they are reviewing the slide), then they can advance using the next button whenever they wish. If it is the first time to see the slide, they cannot use the next button until they have watched the entire slide.

Ashley Terwilliger

Hi Nick,

It looks like Walt covered number 2, so I'll handle 1. 

When you set the player menu to be restricted it impacts accessing the slides from the menu and the ability of the user to jump ahead using the next button on the slide. This was a change from Storyline 1 to Storyline 2 based on user feedback - as if they previously locked the menu the user could just click very quickly to get through the course and not actually have to watch/see everything. I know a few folks have utilized the set up here to allow for restricted menu navigation and for the user to click next at their leisure. 

In regards to your images staying on, I'm having a difficult time following that set up so perhaps you could share a copy of the .story file here (even just one or two slides) so that we could take a look at what you're seeing?

Nick Gregory

Thanks Walt although I think I still need to do my home work on this & watch the tutorials again.What I tend to do is disable the Next button until either  a certain period of time has passed or an animation completed or layers have been visited am I doing the same thing as a variable?

Walt Hamilton

No, hiding the NEXT button until a certain time has passed or some other action has taken place is done with a trigger. Most of us do it that way.

You would use a variable as part of a condition for a trigger.

In the ppt example you posted, the trigger with the variable is set up to hide the NEXT button ONLY if the user has not viewed this slide. An example would be if they view this and maybe start another slide, and in the middle of it find that they are not clear on something that was on this slide. they use the back button until they come to this slide. Since they have viewed it once, the NEXT button is not hidden. This allows them to view only the part of this slide until they find what they need. Then they can click the NEXT button without having to view the whole slide again.

I frequently use variables in my menu. The user is allowed to view non-dependent segments in any order they wish. When a segment is finished, a variable is set. When all the variables indicate that all segments have been viewed, then a button appears on the main menu page that allows the user to advance. The variables do not advance to the next portion. The variables keep track of progress. The button allows the advance, but it doesn't show until all portions have been visited. (I have a very strong aversion to disabling buttons. If I can see it, I am very frustrated if I cannot click it. That's why I hide unusable and otherwise useless objects.)