Forum Discussion
changing state of an object ona different slide
Hi!
there have been discussions on this in the past (over 13yrs ago) and STL has evolved so much since, so the buttons/names in the triggers have changed. i am a newb!
please see the image: can someone help me figure out how I can change the state of objects on slide 1.5 if the user clicks next on slides 1.6, 1.7, 1.8, 1.9, 1.10... and then return to 1.4 because I want to make sure the learner completes those slides before moving on to 1.11?
You can change the object states on 1.5 using variables and triggers with conditions. This post provides details and a demo for how to do that: https://community.articulate.com/discussions/articulate-storyline/create-a-custom-menu-slide
Hi Judy!
thanks for the information. I did that. and it works.
But I also want the learners to be able to click next on each of the slides (1.6-1.10) and trigger the state change on slide 1.5.
Once the learner completes all the slides, the next button on 1.10 makes them jump to 1.5, which only then, will the next button will appear on 1.5.
does that make sense?
Yes, that makes sense.
The basic programming works the same whether the user returns to the menu slide after visiting each section/slide, or whether they step through the sections/slides using the Next button.
In your project, you can still use variables to track that the user has visited slides 1.6 - 1.10.
- Each slide could have a trigger that adjusts its corresponding variable to True. That could be done when the timeline starts, or when they finish any interaction on the slide.
- If they use the Next button to visit each of those slides, all the variables will be True when they return to 1.5.
And the triggers on 1.5 could change the states of the objects when the timeline starts based on the value of the variables.
thanks Judy,
how do I set up the true/false? and the triggers? i have been trying to no avail. i must be doing something wrong
Look at the file attached to the post I linked to in my first reply. That shows what this programming looks like.
For more details, refer to this User Guide info:
