I have a course with a Home scene and 3 other scenes connected to Home. I would like to show a "completed state" for Scene 1 button after all slides in Scene 1 are "visited" (I don't have a visited state set). I would also like this Scene 1 btn to remain completed throughout all scenes in the course.
I set 3 variables to false (one for each button)
Then on each slide:
Adjust variable, variable <button1>, =Assignment, Value of True, When User Clicks <button1>
Then I add the trigger:
Change state of <button1> to Completed, when Timeline starts, object Home Slide, show condition: if value of <button1> equals true.
I know that I am missing something (or many things) and have attached my file here.
One of the challenges you will have is that you have replicated the buttons on every slide. You may want to consider putting those menu buttons on the Slide Master, and then you would be able to build this interaction a little easier.
I think because you have repeated the side buttons on every slide instead of using a master is going to cause a problem. Perhaps look at that before you build the triggers - also I couldn't find the triggers above that you mentioned did you remove them before posting?
I would place a reference to each of the varibles on the home slide to make sure they are operating correctly. If they are I'm guessing its a sequencing problem. I can't see the files now but what you have written looks to be correct.
There are also some other areas where you can probably remove some triggers and make it more efficient. For example, hover state doesn't require a trigger. On the buttons you have a hotspot to that changes the button and text to hover states.
You could get rid of the hotspots and combine the text and buttons. In addition, you can evaluate states. For example, you could have a trigger that says change the state of BTN A to Hover if the State of BTN X is Hover.
I combined the buttons to have one hove state and simplified the triggers. You can see how much the trigger panel cleared up. http://i.imgur.com/tRlZXEw.png
Thanks Ron. I removed all of the triggers and variables and just post the course without anything, then start from scratch again after some assistance from the community.
Ron thanks for the suggestion. I will try to place them on the master slide to condense the work down. This is the first time that I have really jumped into the variables aspect of Storyline 2...it's been an anxiety of mine. :) . I'm sure it will get easier with practice.
Thank you to everyone and Walt for helping me through this. I finally got it to work. I finally understand what Walt was saying all along, which was to set the variable to true on the last slide when a person clicks next, or in my case, I set the variable to true on the start of the last slide. My first big attempt in putting variables into an actual Storyline project and there is no way that I could have figured it out without this dynamo community. Thanks everyone. I'll buy you a coffee at the Food and Beverage Industry Weekly Challenge...let's go :)
Thanks for sharing your learning experience with us, others who read this thread will also learn from it. And it gave me some ideas for a few tips in the workshops.
11 Replies
This post was removed by the author
The Story you provided did not have the above mentioned triggers. Did you removed them?
One of the challenges you will have is that you have replicated the buttons on every slide. You may want to consider putting those menu buttons on the Slide Master, and then you would be able to build this interaction a little easier.
Hi Dana
I think because you have repeated the side buttons on every slide instead of using a master is going to cause a problem. Perhaps look at that before you build the triggers - also I couldn't find the triggers above that you mentioned did you remove them before posting?
Sorry Ron ;-) I didn't refresh my screen before I posted.
I would place a reference to each of the varibles on the home slide to make sure they are operating correctly. If they are I'm guessing its a sequencing problem. I can't see the files now but what you have written looks to be correct.
There are also some other areas where you can probably remove some triggers and make it more efficient. For example, hover state doesn't require a trigger. On the buttons you have a hotspot to that changes the button and text to hover states.
You could get rid of the hotspots and combine the text and buttons. In addition, you can evaluate states. For example, you could have a trigger that says change the state of BTN A to Hover if the State of BTN X is Hover.
I combined the buttons to have one hove state and simplified the triggers. You can see how much the trigger panel cleared up. http://i.imgur.com/tRlZXEw.png
Thanks Ron. I removed all of the triggers and variables and just post the course without anything, then start from scratch again after some assistance from the community.
Ron thanks for the suggestion. I will try to place them on the master slide to condense the work down. This is the first time that I have really jumped into the variables aspect of Storyline 2...it's been an anxiety of mine. :) . I'm sure it will get easier with practice.
Thank you to everyone and Walt for helping me through this. I finally got it to work. I finally understand what Walt was saying all along, which was to set the variable to true on the last slide when a person clicks next, or in my case, I set the variable to true on the start of the last slide. My first big attempt in putting variables into an actual Storyline project and there is no way that I could have figured it out without this dynamo community. Thanks everyone. I'll buy you a coffee at the Food and Beverage Industry Weekly Challenge...let's go :)
Thanks Tom. I actually took the suggestion of adding all of the buttons to the master slide. I did try out your suggestion and it worked perfectly.
Thanks for sharing your learning experience with us, others who read this thread will also learn from it. And it gave me some ideas for a few tips in the workshops.
This discussion is closed. You can start a new discussion or contact Articulate Support.