Forum Discussion
Changing state of buttons after section is completed.
Hey, Jonathan!
What Brother Phil said. He's my guru on variables, along with Steve Flowers. Great folks!
One more thing, since Storyline does not yet have a debugger, you can always put references to your variables on your slides to see if things are working right. Not a true debugger but at least it helps.
I could do things on one slide sometimes and just change object states but that often gets too complicated for me--and very, very complicated slides can often slow the app down (at least they did early in the beta so I've shied away, whenever possible from complicated slides--it also lets me keep things straight and coherent by keeping things simple).
I like to have menu slides where learners can view the main content in whatever order they want. Some of the branched paths from the menu are one slide long (and usually have many layers on them)--while other paths are many, many slides.
Because of this, as Phil's rule of thumb, variables are really the only way to go. So I want to be sure that folks do not get credit for completing a path until they have viewed everything or have done something else.