I am relatively new to Articulate and can't solve this (probably) simple problem.
Namely, I would like the next button to be enabled only when all of the text in the text box appears on the screen.
I am still a bit confused with variables, but I followed some suggestions for similar problems and set some of those with triggers as well. The problem is, that the next button is disabled only for a few seconds, actually, until the animation starts appearing.
As I said before, I would like it though to stay disabled until the animation completes. I attached the screenshot. Hopefully someone can help me. :)
If you want ensure a user stays on every slide until its timeline completes, just set the Player's Menu navigation to Restricted. Then the program will automatically disable Next the first time the user visits the slide.
If you want to control Next on a given slide, use triggers:
A trigger to disable Next when the timeline starts (with a condition to ensure this only happens the first time)
A trigger to enable Next at the appropriate time
For example, in your case, the enabling trigger could be set to run when the animation completes (or when the timeline ends, if the animation lasts until then).
The triggers in the screenshot are set up correctly. However, it looks like the entrance animation only lasts for 1 second.
Since you didn't upload a copy of the .story file, I'll just guess that you set the animation to play "By Paragraph." That will make each item appear separately, so that all the text appears over a longer time, e.g., one second per paragraph. However, the program sees the animation as complete after 1 second, so that's when it adjusts the variable that enables the Next button.
I suggest you do this instead:
Change the "when" for the trigger that adjusts the variable and the one that enables Next, so they both run when the timeline reaches an appropriate point after all of the objects appear on the slide. For example "when timeline reaches 12 seconds."
As in the note I added to the screenshot, there's no reason to have such a long timeline. It'd be much easier to shorten that so you could use "when the timeline ends" for the triggers.
You are awesome! This helped, I adjusted the trigger to 7 seconds and it works perfectly now! Although, I had to shorten the timeline, which I unintentionally extended without notice. :D
4 Replies
If you want ensure a user stays on every slide until its timeline completes, just set the Player's Menu navigation to Restricted. Then the program will automatically disable Next the first time the user visits the slide.
If you want to control Next on a given slide, use triggers:
For example, in your case, the enabling trigger could be set to run when the animation completes (or when the timeline ends, if the animation lasts until then).
FYI: This post has more info about those ways to control the Next button: https://community.articulate.com/discussions/articulate-storyline/tip-controlling-the-next-button-101
Hi, Judy!
Thank you for your prompt reply. I did what you said; it is in the screenshot, which didn't upload for some reason.
I want to control each slide in a different way, I guess, so the restricted option doesn't fit my needs.
Hopefully, this time the screenshot attaches.
The triggers in the screenshot are set up correctly. However, it looks like the entrance animation only lasts for 1 second.
Since you didn't upload a copy of the .story file, I'll just guess that you set the animation to play "By Paragraph." That will make each item appear separately, so that all the text appears over a longer time, e.g., one second per paragraph. However, the program sees the animation as complete after 1 second, so that's when it adjusts the variable that enables the Next button.
I suggest you do this instead:
As in the note I added to the screenshot, there's no reason to have such a long timeline. It'd be much easier to shorten that so you could use "when the timeline ends" for the triggers.
Dear Judy!
You are awesome! This helped, I adjusted the trigger to 7 seconds and it works perfectly now! Although, I had to shorten the timeline, which I unintentionally extended without notice. :D
Thanks again for your patience and promptness!