Using states and triggers to disable clickable objects

Aug 31, 2018

So I have a course where there are three shapes on one of the first screens in scene 1. Learners jump to another scene and then return to this slide at the end of the scene.

I have triggers set up on each shape along with a normal and visited state.

Shape 1

  • Change state to visited when clicked
  • Jump to scene 2 slide 1 (2.1) when clicked

Shape 2

  • Change state to visited when clicked
  • Jump to Scene 3 slide 1 (3.1) when clicked

Shape 2

  • Change state to visited when clicked
  • Jump to Scene 4 slide 1 (4.1) when clicked

Then I have a Next button that has a trigger set the state to hidden when the timeline starts and visible when the state of the three shapes are visited.

This all works so far, but it allows the learner to click the shapes out of order. I don't want them to click out of order.

What is the best method to disable clicking on Shapes 2 and 3 until Shape 1 state is set to visited? I have tried using triggers which properly disables Shape 2 initially, but I cannot get Shape 2 to be clickable when the learners returns to the slide after completing clicking Shape 1 and completing the scene.

Shape 2

  • Change state to disabled when state of Shape 1 is normal (I have also tried state of Shape 1 is not visited)
  • Change state to normal when state of Shape 1 is visited
  • Change state to visited when clicked
  • Jump to Scene 4 slide 1 (4.1) when clicked

 

What am I missing? I want to try this without pausing and resuming the timeline or using variables if I can. Can it be done?

3 Replies
Eric Santos

Hey there, William!  :)

I hope you're doing well.
Kindly check out the attached story file, for the results of my test regarding your concern.
Let me know if this satisfies your requirements.

On your end, you may check the order of the triggers you created, as trigger ordering matters.
Make sure that the changing of state of the next shape happens before you jump to the target slide.
Thanks!

Eric

This discussion is closed. You can start a new discussion or contact Articulate Support.