Drag & Drop: Only continue, if all have been dropped on targets

Hello Beren!

I've seen a few similar questions in the forums before like this one and this one, so hopefully those will get you started in the right direction. I also invite folks in the community to share their ideas, as well!

I believe this sample will be especially helpful with how to handle objects being dragged off the target.

Walt, thank you. The solution you proposed almost worked. We built it up as proposed in your file, but sadly it is with some fast dragging and dropping possible to:

1. Place the items between drop targets, onto the area/shape that is used to see if something has been dragged off targets again. Seems to only happen if the item touches an item that's already been dropped on a target (see attached screenshot, a few pixels is sufficient to make it drop where it is instead of reset to its original position or onto the target)
2. Move items back to their start position very fast will circumvent the area/shape that recognizes that they were dragged off.
3. The area/shape around the drop targets that resets the "draged-on-target" variable if someone draggs an item off target was placed above and below the drop targets as test, with sadly the same problem/outcome.

Any ideas?

Alyssa, thank you, we will try the other solutions now, but we need to figure out something reliable. "Inactive Submit button till all drop items are dropped" has the same issue, "Trigger for when all items have been dropped?" doesn't include the fact that users can drag the items out of their targets and re-set them (as far as I can tell).

Additional:

• We tried to make a fallback with the "object intersect" trigger, so that if items are reset to their original positions by storyline, the "object intersect" trigger will jump in and seit their "dropped"-check variable to false. Seems like "object intersect" only works with manual interaction of the user, not if storyline resets the dropped items onto their original positions.
  
  
• It seems like this is particular to our issue. When the area/shape (that resets the "draged-on-target" variable), which is scaled over the whole slide, it visible, this happens.
  If that area/shape is removed, drop and drag works just fine.
  
  Can someone please confirm? 
  
  Is there a way around that -- something to 100% recognize if items aren't on their drop targets, or dragged out again?

Thanks.

Update:

I got it to work by

• using drop-triggers to set drop-check-variables to true if items are dropped (one for each)
• using "in" intersect-triggers (area covers the original positions) to set drop-check-variables to false if items are returned to their original position
• using "out of" intersect-triggers (area covers the drop target positions) to set drop-check-variables to false if items are returned to their original position
  (yes both intersect checks are needed for a reliable result, otherwise fast-dragging will cause problems)

Disadvantages:

• only works with manual position reset (so if the "one per target" is used, SL resets automatically and that sadly isn't processed/recognized by SL for intersection triggers)
• performance for drag-drop is lower (at least on some browsers), since so much needs to be checked by triggers in realtime it seems
• this is a complex, error-prone workaround if something changes in the future and takes a lot of time to set up and check

I'd wish for an easier more reliable solution in the future. Like using (new) states of the drag-drop items ("dropped" e.g. and "not dropped").

Wow, Beren you were busy this weekend! I'm glad you were able to find a solution that worked for you, albeit not the easiest solution! I know it's something that there have been a few workarounds shared for before, but it's always a good idea to let us know if that makes more sense as a built in feature as well. We use the feedback to help drive our product roadmap, and you can always send along feature requests here. 

Hi - I know this thread is 4 years old but I came across the same problem and had to design a solution. Thinking laterally - rather than testing to see if the items are all intersecting targets, how about testing if any items are left where they were at their home positions?

Works really well.

So - my situation is this. I have three items in the lower half of the screen and three targets in the top half of the screen. I want to make sure the learner has dragged all three items onto a target before they can "Submit"

I set the Drag and Drop Options to "Return item to start point if dropped outside any target". So I know each item is either on a target OR it is in its start position.

I also want a sound to play when the Submit button is clicked (but this is optional).

I have a hotspot off screen. On clicking the Submit Button I set a variable "AtHome" to false and move the hotspot along a motion path that covers the bottom half of the screen. The submit button then plays Audio 1 (the button click)

I have a trigger that AtHome is set to true if the hotspot intersects with any of the three items.

When Audio 1 completes, I move the hotspot back along a motion path taking it back off screen and Submit the Drag and Drop Interaction - but ONLY if AtHome is false

So the Triggers look like this:

When the user clicks Submit

      Set AtHome = value false

      Move Hotspot 1 along a line Motion Path 1

      Play audio Audio 1

When Audio 1 completes

      Move Hotspot 1 along a line Motion Path 2

      Submit Drag and Drop 1 if AtHome = value false

This works for me.... The button clicks but nothing happens if ALL items have not been dragged and dropped. If the user drags an item drops it and then drags it back - still works. 

If I allow a second attempt - still works!! No extra triggers required.

John,

Elegant solution.  Well done.