Drop Correct and Drop Incorrect States Not Working?

Hey, Phil!   Thanks for your reply.  I'm using the "Inbox Drag and Drop" item from the "Top Interactions" template menu.  I made no customizations whatever, other than adding a "Drop Correct" and "Drop Incorrect" state.  And the "suppress" option is not checked on the drag & drop Edit screen.  I was assuming that the items "Drop Correct" and "Drop Incorrect" on the new states drop-down menu were already designed to trigger the character's altered state image based on whether the learner got the question Correct or Incorrect.  Otherwise, why have those specially-named items on the list?  Yet the character's state doesn't alter for a right or wrong answer.  So, something here isn't making sense to me in terms of expected functionality.  Why have those two built-in items if they don't have the appropriate triggers attached?  Seems odd.

And if I am supposed to manually add a trigger to the Drop Correct and Drop Incorrect states, I see on the Trigger menu how I can change the character's state when the learner clicks the Submit button, but not how it's supposed to distinguish between a correct and incorrect answer and trigger the appropriate happy or puzzled expression.

Again, apologies if I'm missing something here, but I really would love to understand how this is supposed to work.  If I need to make my first foray into conditions and variables, that's fine--I just don't see the choices I need there.  But I may just not know what to type in the conditions.  Thanks!

I'm trying to do the same thing.  I have my character state's set up, but I don't see a trigger option regarding the completion of the activity as a whole.

I would love to see someone from Articulate weigh in here...anyone?

Hi Andrew

Sorry been busy.  I have opened the interaction and on the first object added a drop correct, drop incorect state this works perfectly.

But I think what you are trying to achieve, which is to change the state of the character on drop correct has to be manually added

I have added that trigger here, drop correct and drop incorrect are for objects to change state when they are dropped not for when other objects are dropped and therefore require additional triggers to achieve this

Hi, Phil!  Thanks for your efforts, and for that clarification--well, at least that explains it!   Now I know.

I was trying to add a manual trigger to change the character's expression upon a correct or incorrect answer, and can't find or figure out a way to do it.  Under the "When" condition, there is no "User is Correct" or "User is Incorrect".  And if I say when user clicks Submit, I have no idea what additional condition to add to achieve the effect I want.  Is it possible?  If not, I'll be happy to submit this as a feature request, as I'm sure other people would like to be able to do that as a result of clicking a quiz question's Submit button.  After all, assuming you're giving the learner a feedback response on the slide, the character may be visible in the background (if one makes it so), and having them change expression appropriately based on the answer would be a nice touch.

Thanks for any further guidance you can provide!

Hi Andrew, If you just need the character to change state once the submit button is clicked, then all you need to do is add a change state trigger to the relevant feedback layer. See attached.

Nice work Kevin!

Andrew, to answer your question, you can add a manual trigger.  When you convert to free form, the key is to make sure your objects that are being dragged have the drop correct and drop incorrect states added to them (you may need to do this manually).  Once you have these states added to the object, you can address them in the conditions area.  I've attached a .story for you to review.

Hey, Kevin and Mike--thanks!!  I've gone from no solutions to two.    And thanks for the visuals from you both, as well.  That always helps!  Mike, since I was specifically using the default "Inbox Drag and Drop" template that comes with Storyline, and had 5 objects to Drag, Kevin's ended up being the easiest route in this instance.  But I very much appreciate knowing how to follow through from scratch--that will be very helpful.

Much appreciated, everyone!

Hi Storyliners,

I appreciate that this thread is old, but I thought I would "re-open" it as I have a similar issue in that the Drop Correct and Drop Incorrect states aren't being triggered. In my case, I would like the interaction to be submitted using a custom button rather than the player 'submit' button. 

As you can see from the attached file, slide 1 uses the 'submit' button in the player controls and the states work as expected. However, on slide 2, I have the exact same slide but I have added a custom button to submit the interaction and the states aren't being triggered.

Any help on how I can get the states to trigger when using my own 'submit' button would be gratefully received.

Antony

Hi Antony,

I just saw this question and am really hoping someone will jump in and answer it. I'm stumped!

If you go in and Edit the Feedback: Remove the checkmark from "delay item drop states until interaction is submitted", the drop correct and incorrect states, as expected, function properly. So, what is preventing them from functioning properly with a Custom Submit button?

Out of curiosity, I threw together a new Story (just in case something had corrupted yours) and I got the same results.

Can anyone explain how to get this to work? Is it some weird bug?

Hi Rebecca,

I have to admit that this is somewhat frustrating and I too am stumped!

If this interaction was an exercise within my course then I would happily uncheck the "delay item drop states until interaction is submitted" but as it is a question within an assessment, I need to delay these states until the user has made all of their choices.

Fingers crossed that someone out there has a way to get this to work

Hi everyone :)

@Antony - I'm not entirely sure what's breaking the link between the states and the feedback layers when you use the custom "Submit" button, but you can still get this working by using some states and variables for the answers.

I set up a new state and some triggers that rely on conditions for the custom button. I only made the changes for the "Clay" and "Loam" answers, however. You should be able to do this will "Sand" as well. 

I know this isn't exactly what you were hoping for, but hopefully it'll help with displaying the states the way you'd like when using the custom button.

Hi Christine,

Thank you so much for the attached. Whilst your solution hasn't fixed the bug and there is a little more dev to do to create the extra state and add the additional triggers, this still achieves what I want/need - I was in the process of changing the question type and re-designing the whole layout of my intended screen when I saw this come through so you have still saved me a lot of time

Thanks again,

Antony

Hi Antony,

Wonderful :) I'm glad that at least helped a little bit. I'm going to continue to look into this, I think it may be breaking because of the way the default submit button carries over the effects to the layers, but I'm not sure why it would be any different. 

I wish you the best of luck on your project, Antony!

Have a great day,

Christine

Hi Christine and Antony,

I know it's easy to say so now (umm hummm...sure, Becky), but I was going to try triggers to achieve the state changes as well. I didn't because I thought surely Antony and I were missing something, and I didn't want to suggest all the extra work.

Christine, let me (us) know if we should report this as a bug.

Thanks to you both!

Hi everyone,

Whilst Christine's solution worked perfectly, I should add that a further trigger needs to be added to each draggable object that changes its state back to normal when the object is dropped on either of the incorrect drop targets but on condition that the objects state is correct.

I discovered that with the example Christine provided, if you dropped an object on the correct drop target and then moved it to another (incorrect) drop target, it retains the state of 'correct' even though this is no longer true. 

can I make a little adjustment here, why not uncheck the delay drop states, and then set drop correct and drop incorrect to look exactly like normal.  the add a custom correct and incorrect state, on the submit button add triggers to change state of object to correct if === drop correct, etc.  This utilises a bit of the built in logic until it is fixed.

Hi All,

Reattaching the story with Phil's adjustment. Would NOT have thought of that. Renamed the story (for my own benefit). There are 3 slides:

Antony Drag and Drop, Christine Drag and Drop, Phil Drag and Drop.

Want my brain to think like Phil's.

So, to clarify the triggers, here's one example:

Action: change state of

On Object: Rectangle 1 Clay

To state: Custom Correct

When user clicks: Custom Submit

On condition: Rectangle 1 Clay 1's state is Drop Correct

Two triggers for each rectangle: one for the Correct and one for the incorrect states.

Great job rebecca, sometimes i wish my brain would think like Phil's as well

Thank you Christine, Rebecca and Phil for your help here - all suggestions are servicable and I agree with Phil that I/we should be utilising a bit of the built in logic.

@Christine - I'm not sure if you have managed to look further into why the links between the states and the feedback layers aren't working when using a custom submit button, but I would be happy to report it as a bug if required.

Thanks again!

I would report it as a bug anyway the more the merrier

Submitted a feature request. Here are the steps as I reported them. Feel free to C/P and report:

More of a bug plus feature request.
Custom Submit Button doesn't display Drop Correct and Drop Incorrect states correctly on Freeform Drag and Drop.

1. Create drag items and drop items.
2. Assign Drop Correct states on drag items and format, e.g., green fill.
3. Assign Drop Incorrect state on drag items and format, e.g., red fill.
4. Convert to freeform...leave all defaults.
5. Create custom submit button (trigger: submit interaction drag and drop).
6. Preview the interaction. Drag the object(s), correctly or incorrectly, and use Custom Submit button. Formatting does NOT appear.
7. Replay the slide, drag the object(s), correctly or incorrectly and use Standard Submit button, formatting does appear.
Request: Custom Submit button should behave in like standard submit button.

BTW, I tried to Submit via FF (20.0.1) and the page just sat there FORever. Submitted via IE. I have a LOT of trouble interacting with Articulate support via FF for many FF versions now.

Good morning!

Sorry for the delay, everyone.

Thanks very much for that request/report, Rebecca! It's definitely something we'll want to look in to. 

In regards to the Firefox trouble, I'm not sure what's going on there. I'm afraid I don't use Firefox very often (unless I'm testing a course), I mainly use Chrome. Was it just with the feature request form, or have you had trouble with the case forms, or others as well?

I will take a look, though, and if I see the same issues I'll pass the information over to our web team. 

Thanks again!

Christine