Return state to normal on a Drag & Drop question

Oh wow Sara I thought I posted this days ago. I am so sorry Here is a fix without all the different layers.

Regarding the original issue, as I've tested this issue several times, there is no way to get the draggable item to return to its "normal" state. Once it goes to "drop correct" or "drop incorrect", it never returns to "normal" even if the item gets moved back to its original starting point (whether by user or automatically). This seems to be a bug to me and has caused me fits. Any insight or is this a bug as I've concluded?

Hi Jason,

What state do you see it "return" to when dragged back? Are you using Storyline 1 or Storyline 2? I see that there is an issue within SL1 that it doesn't return to it's normal state in HTML5 only - is that where you're seeing it? I also see that this behavior does not occur in SL2. 

I'm using SL2 and this is for Flash. It always stays in either of the last states it has entered, whether "drop correct" or "drop incorrect". Getting it to go back to "normal" never happens--whether you manually drag it back to starting position or the built-in interaction "snaps" it back. You can clearly see that the item has visibly returned to the "normal" state but for triggers, it doesn't recognize it.

Hi Jason,

I'd like to take a look at what triggers you've set up for this. Often, applying additional custom triggers to a drag and drop interaction overrides the built in drag/drop settings and that could be interfering with your normal state triggers. Can you share that one slide from your .story file? 

Hi Jason,

Sure you can send it along to me here. 

Thanks. I submitted my file there.

Thanks Jason, I'll respond through the case. 

Hi Jason,

Thanks again for sharing your file. I sent you a reply earlier but also wanted to share it here in the forums. After reviewing your file and setting up a similar behavior on a brand new file, I was able to replicate the issue you are experiencing in regards to the submit button not adjusting it's state to normal based on all the drag items being "not normal" state. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try adjusting the submit buttons state based on the state of the drag items being correct or incorrect which would need to be two triggers, but that worked as expected for me.

I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future. 

Can you share your "2 trigger" file with me so I can see how you did it? I did start to go down that road but the problem is that the approach doesn't work the same.

In this example, I want to know when 6 items are NOT a certain state. The easiest thing to do is set up the trigger I did but unfortunately it doesn't work--as you've found (thanks!). To go through a "back door" approach like you're proposing, I'd have to find out when these same 6 items ARE 1 of 2 other possible states--we have 3 states; normal, drop incorrect, drop correct.

If I really only care about them leaving the normal state but can't read the normal state accurately, I'd need to know if they are ANY of the possible combinations: 1 = drop incorrect, 2 = drop correct, 3 = drop correct, and so on. You can see that the combinations get pretty complicated quickly and Storyline can't give me what I need with 2 triggers. The 2 triggers I think you're referring to are when all 6 ARE drop correct and another for when all 6 are drop incorrect. However, that is only 2 possible solutions for a combination that produces many, many more. For instance, 3 could be "drop correct" while the other 3 could be "drop incorrect" and that would satisfy my goal. Unfortunately, triggers only let you daisy chain with AND or OR, and not combinations of the two like you would would with programming languages. I wish they would add this functionality and your solution would be almost as straight-forward as my original one.

Thanks!