Forum Discussion
Next button?
Hello - I have disabled the next button until 3 boxes are clicked to show layers of information. I can't get the next button to pop back up though. I don't have this problem when I am using buttons because I just change the state of the next button to normal once buttons are visited. But when I am using a box/square I can't figure out the work around.
I have a variable that's T/F with a trigger that sets state of next button to normal once variable is true and rectangle 1, 2, and 3 are selected. I'll include the file below if someone can help.
I am referencing the first scene, slide 1.4
Any object (text box, shape, picture) can be given a Selected and/or Visited state. Those states will function just like the ones on a button. Thus, a trigger can look for the Selected or Visited state on those objects.
Here's the problem: The trigger to change Next to Normal runs when a variable changes. But there's no trigger on that slide to change the variable, so the trigger will never run.
- If you change that trigger to run when the rectangles reach the Visited state , the Next button will change to Normal when the third rectangle is clicked.
Other things to consider:
The trigger to disable Next will run again if the user revisits the slide. To fix this, add conditions, so Next is disabled when any of the rectangles ≠ Visited.
- It's more stable to use "≠ Visited" (is not Visited) as a condition, instead of
"=Normal" (is Normal). As Super Hero WaltHamilton once put it: Like us, every state thinks it's Normal. In other words, Normal underlies every state, so the "=Normal" condition doesn't always work as expected.
You don't need to have a text box on top of the rectangles. You can enter text directly into a shape. Just double-click it, and start typing. As needed, go to Format Shape>Text Box to adjust the margins of the shape and the text placement.
Here are the best practices for uploading a .story file:
- 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.
FYI: Here's more info about controlling Next: TIP: Controlling the NEXT Button 101 | Articulate - Community
8 Replies
Hello - where can I view the changes?
I'm sorry I though I attached the file.
I made some changes that might help.
Any object (text box, shape, picture) can be given a Selected and/or Visited state. Those states will function just like the ones on a button. Thus, a trigger can look for the Selected or Visited state on those objects.
Here's the problem: The trigger to change Next to Normal runs when a variable changes. But there's no trigger on that slide to change the variable, so the trigger will never run.
- If you change that trigger to run when the rectangles reach the Visited state , the Next button will change to Normal when the third rectangle is clicked.
Other things to consider:
The trigger to disable Next will run again if the user revisits the slide. To fix this, add conditions, so Next is disabled when any of the rectangles ≠ Visited.
- It's more stable to use "≠ Visited" (is not Visited) as a condition, instead of
"=Normal" (is Normal). As Super Hero WaltHamilton once put it: Like us, every state thinks it's Normal. In other words, Normal underlies every state, so the "=Normal" condition doesn't always work as expected.
You don't need to have a text box on top of the rectangles. You can enter text directly into a shape. Just double-click it, and start typing. As needed, go to Format Shape>Text Box to adjust the margins of the shape and the text placement.
Here are the best practices for uploading a .story file:
- 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.
FYI: Here's more info about controlling Next: TIP: Controlling the NEXT Button 101 | Articulate - Community
Thank you for all of the tips. This was the first question I posted. I did this
- If you change that trigger to run when the rectangles reach the Visited state , the Next button will change to Normal when the third rectangle is clicked.
and the next button is still not appearing.
Here's a file with the trigger I suggested. It works for me.
FYI: I also put the labeling text directly into the rectangles. And I renamed the rectangles. For troubleshooting, I also changed the Visited state so it's visibly different than Normal.
One more thing: there are triggers that change the rectangles to Normal when the main audio completes. If a user listens to the audio after clicking one or more rectangles, those triggers would change the rectangles back to Normal. And that could prevent Next from enabling.
