How do I set states for drag and drop interaction?

Jul 22, 2013

Hi all

Me again!

I seem to be having problems setting states in a drag and drop interaction so that I can make an 'unfinished interaction' message show up at appropriate times. I've tried a number of things, but they either don't seem to work at all or they mess up the interaction so that even when the learner has completed the interaction they can't submit it for results. I have two goals: set up the 'unfinished interaction' message, and set rules so that they can't continue to the next slide without completing the interaction. (Same thing, but I'm guessing they require two different processes.)

I've attached the file here.

* The first screen is my original interaction, but with the attempt to put an 'unfinished interaction' message. As you can see, it disallows the learner to click submit once finished. I then changed the interaction entirely, thinking that using buttons was probably a bad idea (not just in terms of interaction problems, but also confusing the learner.)

* The second is where I'm at right now.

* The third is one more attempt that didn't work, though I suspected as such with the 'hover' aspects.

I've also tried a true/false variable with no luck.

My last option is to simply make the options 'bounce back' from an incorrect drop target, but I don't think this provides the best learning experience.

Please help!


11 Replies

I think you were mostly there. I changed the rules on your completed check to use an "OR" condition instead of "AND".

I added a mask on your false layer to hide the user's incorrect responses on the base layer.

and I added an advance action to the button on your correct and incorrect layers right after the hide layer action you already had.

seems to be working ok for me.


Sometimes, I've found that using the State of An Object as a trigger can result in unwanted behavior.

You might try using variables instead.

I also noticed your target boxes are not labeled correctly so even when I performed the actions correctly, (according to the correct state) I was marked as being wrong.

Lastly, layers sit on top of the base but do not hide the base. This means that when you are providing the users feedback, they are seeing their responses below the correct responses you are showing them. It creates a jumbled mess.

Use a white box on each layer to mask the background to address this issue.

Lil Monk

Hi Owen

I understand what you're saying about the jumbled mess. I had created a complete white layer on the feedback screens for the original interaction. I just hadn't got the new interaction working in a fundamental sense so that would have been dealt with once I'd seen it.

I honestly don't know what happened with the labelling of the target boxes, however I have already seen these and fixed these.

One thing you probably have not noticed yet is that the interaction is also getting 'stuck' at times. I can put one or two things into the boxes and then I cannot move anything else. There does not seem to be any rhyme or reason to that issue.

I'll try the variable method again, but that hasn't seemed to be working either. I'll also try changing the order of the triggers.


Lil Monk

Hi Owen

I changed the order of the triggers as you suggested and it did work in the file that I've posted here. Then I pasted it back into the original course and it was temperamental again - not allowing me to finish the interaction (after moving a couple of terms) and also showing the 'unfinished' message when I press submit. The simple answer to this problem is to take out the 'unfinished interaction' message. It should be obvious to the learner that they need to complete the interaction first, but I was trying to be consistent by having that on any screen that has any interaction. There seems to be some kind of issue with using states in drag and drop interactions from what I can work out, as that was all I changed in the original interaction for it to go awry.

Thanks for your help!

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