Forum Discussion
Drag and Drop Interaction
If you attempted to recreate the Rise sorting activity discussed in this thread, then quite a few steps may have been missed in order to get the interaction working correctly. I would suggest reviewing my Storyline file again and then recreating the interaction one element at a time.
There are several variables involved that help reset drag objects back to their Normal state when they are returned to their original position via motion paths after being dropped on an incorrect target. Additional triggers tied to the motion path completion then set certain drag objects to a Hidden state when dropped on a correct target.
The reason the drag objects are not returning to their starting position after an incorrect response even though "Return item to start point if dropped outside a correct drop target" is selected, is that the built-in drag-and-drop behavior has already been overridden by your custom triggers and animations.
As a quick test, try disabling the Emphasis Animation triggers for the drag objects and then preview the slide again. If the objects start returning correctly, you'll know that one of the custom triggers or animations is interfering with Storyline's default drag-and-drop functionality. Or simply disable or remove all triggers to test it out.
My recommendation would be to compare your setup against the sample file step by step, paying particular attention to the variables, motion path triggers, and state changes, as these elements all work together to achieve the desired behavior.
Sometimes when a selected option isn't working, the fix is to deselect it and then select again. That's what I did with the "Return item to start point..." option in the edited slide of the attached file.
- Note: When dropped outside of a target, the draggable item will change to its Drop Incorrect state when that change isn't delayed until the "Submit" trigger. To avoid that, you could delete the Drop Incorrect state and use a custom state instead. In that case, you'd need to trigger the change to the custom-incorrect state when the object is dropped on the incorrect target.
As for the objects disappearing, consider this trigger:
That would immediately Hide the object when dropped.
Here's are the triggers I used for the Westgate object instead:
Note that I added a Pulse animation so there would be something to measure the delay before the object is hidden.
I only adjusted the triggers for the Westgate object. You'll have to fix the others.
Also, delete triggers like these:
If the user happens to click on the screen, the objects disappear before they can be dragged.