Forum Discussion
Story line issue when you revisit a slide
JakeDelaney : The "Resume Saved State" slide property will work during Preview. (The "resume" function that won't work is resuming the course where you left off if you exit the course and then relaunch it. That function works when the published course is in an LMS/LRS.)
The attached file has edited versions of the slides that work as expected. Here's some of what I did:
On both slides:
- Put the title of the each button into the button (instead of having all the titles in a separate text box).
- Deleted unused states, and inserted a checkmark in the Visited state. FYI: That was just a quick way to create a visible difference between Normal and Visited. There are lots of other design choices that could be used.
- Renamed some of the objects and layers in a way that makes troubleshooting a little easier.
- I also made a few changes so I wouldn't have to listen to the audio when testing, either by hiding the audio in the timeline or disabling the triggers that play it. (I don't like being forced to listen to audio that reads the text when I'm taking a course. I especially don't like it when troubleshooting.) I also added triggers to the intro-text boxes, so I could hide them by clicking for quick testing.
On the first slide:
- Added conditions to the trigger that hides the "Definition Central" button. This was done to ensure that the button wouldn't be re-hidden if the user returns to this slide.
- Deleted triggers that change the buttons to Visited. Any object with a Visited state will automatically change to that state when clicked. Here's more info: PRIMER: Take advantage of built-in states | Articulate - Community
- Moved the trigger that adjusts the value of "Lawfullypresent" so it's before the trigger that jumps to that slide. Trigger order matters. When the program jumps to another slide, it can't run any triggers back on the original slide. So if you want something to happen, it has to be done before jumping away.
On the second slide:
- Added conditions to the trigger that hides the Return button. This was done to ensure that the button wouldn't be re-hidden if the user returns to this slide.
This post might help for future reference: TIP: Controlling the NEXT Button 101 | Articulate - Community
Thank you so much. I tried doing checkmarks in the past and didn't get it to work, what are the steps for that?
The way it was explained in your message was great, and I appreciate the help. I myself has gone back and forth on the audio but it seems like it is something we want them to listen to. I used the dialog boxed to hide it. If there a way to get audio to play if they want it to and not play if they don't?
When you're editing states, you can insert anything—a shape, an icon, etc.—into a state.
- This might help: TIP: Making icons easier to program and easier to click | Articulate - Community
- See the Combining States slide in this project for info about how extra objects appear: https://360.articulate.com/review/content/eaccc037-929b-43b5-b636-5333181a9c70/review )
There are different ways to control whether audio plays or not. For example, the file could be on its own layer, with a button that shows the layer and plays the audio.
Another option would be to always play the audio, and let the user click something to show or hide captions.
If you search the community, you should be able to find more info and even example files for control audio and how to toggle settings. If you still need help, it'd be best to start a new discussion.
BTW, since you're just starting with Storyline, I recommend bookmarking the User Guide. It's a great source for basic info. If you don't see exactly what you're looking for in the TOC, go to a related topic. Most of the articles link to additional details.
Good luck!