Have a look at this .story file, which does what you want (I think...), and which might help you decipher the steps necessary.
It is slightly different from the solution suggested by Adrian.
I have always used a custom button for this operation rather than Visited, as Visited can cause the button state to change a split-second before SL actually moves to the next area you want to view, which is "sub-optimal" if the state is very different, for example - has a "check-mark" over the menu button.
3 Replies
Hi Jeff,
Take a look at this article.
Always Happy to Help,
Adrian
Hi Jeff,
Have a look at this .story file, which does what you want (I think...), and which might help you decipher the steps necessary.
It is slightly different from the solution suggested by Adrian.
I have always used a custom button for this operation rather than Visited, as Visited can cause the button state to change a split-second before SL actually moves to the next area you want to view, which is "sub-optimal" if the state is very different, for example - has a "check-mark" over the menu button.
Hope this helps.
Bruce
Thanks, Bruce, that worked well! I love how easy it is to use variables in Storyline.
This discussion is closed. You can start a new discussion or contact Articulate Support.