Forum Discussion
Need help making not started, in progress and completed triggers for menu bar?
I have a menu that includes states, and they are not started, in progress, and completed. When someone clicks. when they have got to the end of module 1, it will then change the state on the menu to completed, but it is not working.
Not sure what I am doing as I followed videos and other discussions and did what they said, and it still is not working.
The project is not fully done, so the sizing of text needs changing, just want the menu to work with the variables and triggers.
9 Replies
First of all, you don't need the triggers to change the state to Not started. Just set that as the Initial state.
You also don't need any of the Mod[#]InProgress variables. You can simply change the associated unit label to the In Progress state when the user clicks the button to start that unit. Just be sure that trigger comes before the one that jumps to the unit/scene. (A trigger can't run if the program has already jumped to another slide.)
- Note that in my example above, I renamed the objects. I suggest you always give meaningful names to objects involved in an interaction (especially when you're asking for help). That makes developing and troubleshooting much easier.
Finally, you can change a unit label to Completed when the timeline of the slide starts with a condition that the associated variable = True. (I assume you change it to True at the end of the unit.)
- Note: A "when timeline starts on this slide" trigger will always run when the user reaches a slide. That's true even if the Slide Properties are set to Resume saved state.
Hi, thanks for this, but still not working. I did what you said, and it's still not working. When I click the button unit 1, it changes the state to in progress, but then when I go to the module 1 and then back button or home button it goes back to not started state, and I want it to say in progress
I have attached what I have done so far
Change the Slide Properties to "Resume saved state." That kept Unit 1 in the "In Progress" state for me.
- For quiz slides, it is best to leave "When revisiting" at "Automatically decide." That allows the built-in functions for reviewing and retrying to work.
- For all other slides, I recommend changing the setting to indicate exactly what you want: either "Reset to initial state" or "Resume saved state."
Note: This project is quite large. When asking for help here in the community, create a copy that only includes the slides needed for troubleshooting. And, for future reference, I suggest you set up and test this kind of programming before adding all the content slides.
By the way, the text in the Unit 1 and Unit 2 labels has "Not stared" (instead of "Not started").
Judy, thanks for the help and tips. This is my first question/discussion. I was thinking the course might have been a bit too big to share.
For reference for if/when you start a new discussion, here's my standard advice about uploading .story files here in the community:
- Only include slides that are related to the problem.
- Be sure objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.
- Be sure to clearly describe the following in the file and/or in the post with the attachment: What you want to happen, what is not happening that should happen, what is happening that should not happen, and what you have already tried.
Admittedly, some problems seem to involve the entire course. But there are still usually ways to pare down the file. For example, with a problem like the one you encountered, the troubleshooting only needs the custom menu slide and one slide in each section. In fact, I only tested with the menu slide and one slide in one section.
By the way, you can find my troubleshooting tips here: TIP: The Eightfold Path of Troubleshooting | Articulate - Community
Best wishes with your projects!
I think the current setup might be overcomplicating things by using multiple True/False variables to manage just a few status values. Instead, you could simplify it by using text variables that switch between "Not Started", "In Progress", and "Completed".
Also, unless you're using state changes on text boxes to visually indicate something specific (like applying colors to shapes based on status), there doesn't seem to be a strong reason to handle it that way. It might actually add more confusion to the setup.I’ve created a simple demo using 4 text variables to track 4 chapters. Each variable is displayed in its own text box, and the status updates automatically as you move through the slides. Each chapter in my example has 3 slides. The corresponding text variable updates to "In Progress" when the first slide of the chapter is reached. It doesn’t change when returning to the menu unless the last slide of that chapter has been visited, in which case the variable updates to "Completed".
Check it out and see if it could simplify your current project.
