Triggers on a submit button for drag and drop

Thanks Luciana

Yes, Mick made a suggestion, though as I started suspecting it requires a very elaborate setup! 

I've opted for just removing one of the prevention strategies so there is enough space for the submit button, but here is Mick's advice, for anyone who comes across this thread at a later date in need of the same or similar solution:

You will require T/F variables for each drop target that will change value when the learner drops the object on any drop target.

1. You need variables that will correspond to your Drag objects like this:
https://sharing.articulate.team/OAuvqb1G

These variables will change in value when the learner drops these to the target objects:
https://sharing.articulate.team/kpuvbLx7

2. Then you need a Toggle Trigger that will change to True, which will cause the state change to happen. It will also include T/F conditions, so it will only be satisfied when all T/F variables corresponding to each drag and drop item are all true, meaning all drag items have been moved to all drop targets.

https://sharing.articulate.team/nOu2k82Q

Hi Walt

Thanks for taking the time to reply. It seems the ORs and ANDs may be bunched as even a much simplified version of your suggestion doesn't work. I've submitted a support case and will post the solution here once received. Else I may just need to cut down options on that slide! I am intrigued whether it can work though...

Start with the Submit button in Hidden state

Create the trigger:

Change state of Submit to Normal When Object 1 is dropped on [any of the targets] if Object 2 is Drop 
Correct Or Object 2 is Drop Incorrect And Object 3 is Drop Correct OR Object 3 is Drop Incorrect And etc.

You will need one of these triggers for when each object is dropped.

I think this will work, but I’m not currently with SL to test it. It depends on how it combines the Ors and Ands. If it bunches the ORs, then The ANDS, it will work. If it just runs through linearly, it probably won’t. In that case, you will have to create the checking one step at a time. Unfortunately, SL doesn’t have a Dropped state at this time, so you will need a variable for each object to show if it is either Dropped Correct or Drop Incorrect. Then each time an object is dropped, check the other objects to find their state and set their variable, then another trigger to show Submit if all the variables are True.