Variables a go go
Oct 22, 2015
By
DJ Trent
I have an entry slide with 5 clickable rectangles. Each rectangle goes to a (scene) path. The last slide in the path (each scene) has a trigger to change a true/false variable to true with a click on a hotspot. The initial state of the variable is false. I hide the Next button when the timeline starts.
I have an additional variable that "should" redisplay the Next button when all 5 of the scene variables are true and the page visits variable is >= 5. Doesn't seem to work. Any thoughts?
The story is too large to upload, so I'll add images of the triggers.
Thanks for any help.
7 Replies
T/F is a toggle and if by any chance you clicked the same object twice you just reset it to False and your trigger won't work. Try a number variable; i.e. 0 vs 1 and your (when it is equal to 5 , then) logic will work.
p.s: better set it to "greater or equal"
Seth: You rock. That was smooth as silk.
I did not know that it was a toggle. Good info.
Thank you.
Glad that Seth was able to assist you here DJ.
For you or anyone else that may run across this thread, here is our documentation on adding variables.
Darn it. I spoke too soon. It worked once, in preview, but won't work at all in published material.
I'm attaching my triggers and a shot of my entry slide. I've put counters on the entry slide for each variable. I can see that all the Next button trigger requirements are met, but the button just doesn't show up.
Thanks to all for the info!
I've done exactly this same kind of thing but I set it up a different way.
The way I would do it is this:
It's true that in this case, I had to duplicate a lot of checking of variables, but I've found that this method seems to work most of the time and all the checking and variables are handled on this one slide and not flung across a bunch of scenes.
I hope this helps!
DJ,
It's very easy. Hack this.
Now that worked. It was all in the stack. I kept the "greater than or = to 1" instead of T/F, but everything else worked great. Thank you.
This discussion is closed. You can start a new discussion or contact Articulate Support.