The slide didn't show accordingly based on leaner's selection

May 28, 2018

Hi,

I am designing a project in which the next slide should show the corresponding one according to the learner's selection (among 3 different items, size, color and steps).

For example, when the leaner selects big, red, 2 steps, next slide will show 1.10 Big+Red+2. When the leaner selects small, black, 3 steps, next slide will show 1.32 Small+Black+3. In my attachment, it always show 1.2 Big+Pink+2 (frustrated). Is any trigger wrong?

Additionally, i am using 'drag and drop' to have an interaction with learners. There are 16 different scenario shown based on learner's selection from the variables of 2 sizes (big/small), 4 colors (pink/red/black/yellow) and 2 steps (2 steps/3 steps). Is there better way to design instead of having so many slides?

Thank you so much!

Walt Hamilton
Hero

almost 6 years ago05/28/18 at 1:50 pm (UTC)

This trigger is your problem:

When expanded, it looks like this:

This says that you should jump if the slide 2.1 is dropped on 2 steps, or Big, or Pink. For it to work, you need to set it to jump if Big is dropped on column_Size, (or Pink on color, or steps on steps).

Which brings up another problem. If it jumps when the size is chosen, you can't choose color and steps.

But since the slide isn't dropped on any of the drop targets, the only way to advance is with this trigger:

It always jumps to the Next slide, which is Big+Pink+2.

As to your second question, yes there is a much easier way to do this.

I changed the trigger philosophy two ways.
1. Instead of triggers to make objects hidden on timeline start, I set their initial state to hidden, and saved a lot of triggers.
2. When an object is dropped, I change a variable. Then everything appears or disappears when the variable changed.
There are three advantages to this:
1. Most importantly, "When variable changes ..." always initiates triggers, while "When state of ..." is known not to function under certain conditions.
2. Using the variable change to fire the triggers allows me to use only one instance of "When object is dropped on ..." which in my (and your) experience has proven to be confusing and vulnerable to mistakes.
3. Instead of a 3 triggers to change Pink to hidden (one if black is chosen, one for red, and one for yellow), you can use one trigger to hide pink when any other color is chosen (Variable Color is changed.

Using the variables has cut the number of triggers by nearly half.
It has moved the triggers so that they are listed all together, instead of attached to an object. You may find that more confusing, or less confusing. Personally, I like it. You can read down the trigger list and see what happens: When one size is chosen, the other is hidden, and the colors become visible. When a color is chosen, the others are hidden, and steps become visible.
Then I used layers to show the final result.
I used Height and Width to show Size. By showing the size as text instead of a graphic, I was able to cut the number of layers in half.

Attached find the three slides that illustrate these changes.