I am trying to make a freeform which the user need to drag and drop item on a RNA structure. so I validated the drag and drop itens, but didn't linked with a right answer, because I need a multiple Drag and Drop question. So I used the state status to change to drop correct or incorrect. It is ok to do that. But the drag itens are keeping their last status when returning to start point when another drag item is dropped on(I activate the option allow one item on each drop target). so now, I don't know what to do to make them return to normal state eigther.
Someone can help me?? I can provide the .story if you need!!!!
Well, then it would be considered "dropped" so the variable would have changed. I know it's not a perfect method, but it's a workaround until we hear from the QA team.
We ran into a similar issue. When the user drops a draggable it would either play a "correct" sound or a "wrong" sound based on the state of the draggable. However the sound would only play once from some items dropped on an incorrect target. The draggable would snap back to start but the state would remain DropIncorrect.
To get around this bug I added a trgger for each draggable to the "wrong" sound. After the audio plays it cycles through all draggables and resets all the states to Normal EXCEPT those that are DropCorrect.
Add a sound to your file (a couple seconds of silence) attach the riggers and it should work .
Thanks Randall for sharing that workaround here and I'm glad you've got it working. If you're able to share a sample file that may help others visualize what's occurring.
In my case however, the draggable items never return to a Normal state, so
I believe this is a different issue. Thanks for your suggestion though.
Ashley, can you check with the technical team to see if there's been any
resolution to my issue?
Hi Jason, My draggables were not returning to the Normal state either which is why I added the trigger to set it that way when the audio file completes.
here is a sample file. In my case I had different sounds playing when an item is dropped correctly or incorrectly. You could replace the sound with a recording of silence. You just need a media file of some sort to launch the trigger.
Thanks for checking in. The issue I filed is still with our QA team and as such I don't have any additional information to share. This thread and the case where you shared the file are marked for follow up once there is additional information to share.
I can't say if it's something that will be addressed in the future as a new feature, as we don't share information in regards to our product road map or timelines, but it's worth sharing your thoughts in the form of a feature request. As I understand it, it was built that way based on instructional design principles so that users would know how they previously answered the question.
This should be AN ESSENTIAL feature. I have created a thread in the past and i'm glad to finally come across others who share the same issue so I realise now there's no point in me wasting hours of my time trying anymore, which I unfortunately have done due to not having a solid answer on whether or not it can be achieved on my post.
I can't even get a drag and drop to function without this to be honest. I want my submit button to only appear when a drop target is in use and it is IMPOSSIBLE. This means that the button can appear from 'hidden' to 'normal' (Not using the built in Drop states but that's another bug in itself) when the drag items are dropped on the drop targets but if one returns to initial start point (due to having another drag object being dropped on and the one in place being reset) you cannot change the state of the drag object back to normal.
Basically what is needed is either to be able to reset state to normal when not dropped on a target OR a trigger which recognizes that a drop object is in use. So we can trigger the submit button to disappear again when the object is NOT IN USE.
2016 Now, this should be basic drag and drop functionality to ensure users can actually only submit an answer, when an answer is actually given, not just floating around or back in it's usual starting point.
Hi Aiswarya! I'm happy to dig into this with you. Can you tell me more about the problem you're facing? Are you trying to design a drag-and-drop quiz slide?
If you're able to share a sample file with a slide or two, that would be super helpful!
Hi,
In free form drag and drop template, first we dropped the object to any of
the target position then we again drop the another object on top of the
first object. At that time the first object return to its initial location
but its state not return to the normal, it is continuing in dropped state
or drop correct or drop incorrect state. Because of this we cannot identify
the player filled all the drop target locations. Can you help me to solve
this problem.
Hi there, Aiswarya. Thanks for giving some detail about what's happening in your file. I made a 2 minute Peek screencast to show how the drop states should work in Storyline 3.
You'll want to create Drop Correct and Drop Incorrect states for your drag items:
In the Drag & Drop Options menu, choose to allow only one item in each drop target. Also, uncheck the box to delay item drop states so you can immediately see the Drop Correct/Incorrect states:
When you drag and drop an item on a target, you should immediately see the Correct or Incorrect state. If you drop another item on the same target, you should see the first item move back to its original position, and return to a normal state.
If you manually drag an item back to it's starting location, however, it's considered a "drag-and-drop," and you'll see the Drop Incorrect state.
Let me know what's happening in your file! If you can share some screenshots of your setup, or better yet, an example .story file, that would be so helpful. Use this link if you need to keep it private. Thanks!
@Crystal Horn Your screencast shows how it's supposed to work, which Storyline version were you using? Could you share your test file to see if it behaves the same on my machine?
I tried 3.3.1, 3.4.1, 3.5.1, and the current Storyline 360 version - none of them reset the state of the swapped out drag item :(
Hi there, Jasmin. I was using Storyline 3 update 5 in the above example. I don't have the same source file, but here's a new one with the same setup described above.
What are you seeing on your end? If you'd like to share a screencast or your .story file, I'm happy to have a look! You can share your file publicly here or privately using this link. I'll delete it when I'm done troubleshooting.
This should be AN ESSENTIAL feature. I have created a thread in the past and i'm glad to finally come across others who share the same issue so I realise now there's no point in me wasting hours of my time trying anymore, which I unfortunately have done due to not having a solid answer on whether or not it can be achieved on my post.
I can't even get a drag and drop to function without this to be honest. I want my submit button to only appear when a drop target is in use and it is IMPOSSIBLE. This means that the button can appear from 'hidden' to 'normal' (Not using the built in Drop states but that's another bug in itself) when the drag items are dropped on the drop targets but if one returns to initial start point (due to having another drag object being dropped on and the one in place being reset) you cannot change the state of the drag object back to normal.
Basically what is needed is either to be able to reset state to normal when not dropped on a target OR a trigger which recognizes that a drop object is in use. So we can trigger the submit button to disappear again when the object is NOT IN USE.
2016 Now, this should be basic drag and drop functionality to ensure users can actually only submit an answer, when an answer is actually given, not just floating around or back in it's usual starting point.
More than 3 years and I'm facing the same issues like Lewis described... I know, there is a solution where I have to use a hugh amount of triggers. However, an interaction as essential as "drag and drop" should work without such errors. So: Is there any update regarding this problem?
It's been five years and still no resolution here?
I have this same issue - the object's state does not go back to NORMAL state upon kicked from the target point where another item is dragged to the target point which has already a dropped item. I used variables and state triggers for dragged and dropped objects to debug but still cannot solve this one. I hope Storyline360 should check this drag and drop 'state' issue.
I'm having the same issue. I've tried all kinds of triggers and variables, to no avail. This really needs to be an essential feature, as other users have mentioned. I'm posting here, because I'm hoping that the more users that post about this, the more likely it will be fixed.
I concurr. I've wresteled with the same issue without a decent workaround. I agree with all that have said this should be an essential feature. Several comments over the years should warrant immediate attention.
53 Replies
Well, then it would be considered "dropped" so the variable would have changed. I know it's not a perfect method, but it's a workaround until we hear from the QA team.
We ran into a similar issue. When the user drops a draggable it would either play a "correct" sound or a "wrong" sound based on the state of the draggable. However the sound would only play once from some items dropped on an incorrect target. The draggable would snap back to start but the state would remain DropIncorrect.
To get around this bug I added a trgger for each draggable to the "wrong" sound. After the audio plays it cycles through all draggables and resets all the states to Normal EXCEPT those that are DropCorrect.
Add a sound to your file (a couple seconds of silence) attach the riggers and it should work .
Thanks Randall for sharing that workaround here and I'm glad you've got it working. If you're able to share a sample file that may help others visualize what's occurring.
In my case however, the draggable items never return to a Normal state, so
I believe this is a different issue. Thanks for your suggestion though.
Ashley, can you check with the technical team to see if there's been any
resolution to my issue?
Hi Jason, My draggables were not returning to the Normal state either which is why I added the trigger to set it that way when the audio file completes.
here is a sample file. In my case I had different sounds playing when an item is dropped correctly or incorrectly. You could replace the sound with a recording of silence. You just need a media file of some sort to launch the trigger.
Hi Jason,
Thanks for checking in. The issue I filed is still with our QA team and as such I don't have any additional information to share. This thread and the case where you shared the file are marked for follow up once there is additional information to share.
This post was removed by the author
Hi Jean-David,
There is not a change in the behavior of the drag and drop, as they won't reset to their initial location based on a reattempt of the slide.
This post was removed by the author
Hi Jean-David,
I can't say if it's something that will be addressed in the future as a new feature, as we don't share information in regards to our product road map or timelines, but it's worth sharing your thoughts in the form of a feature request. As I understand it, it was built that way based on instructional design principles so that users would know how they previously answered the question.
This post was removed by the author
Thanks for sending along the feature request Jean-David, it's certainly not the first one I've heard of!
This should be AN ESSENTIAL feature. I have created a thread in the past and i'm glad to finally come across others who share the same issue so I realise now there's no point in me wasting hours of my time trying anymore, which I unfortunately have done due to not having a solid answer on whether or not it can be achieved on my post.
I can't even get a drag and drop to function without this to be honest. I want my submit button to only appear when a drop target is in use and it is IMPOSSIBLE. This means that the button can appear from 'hidden' to 'normal' (Not using the built in Drop states but that's another bug in itself) when the drag items are dropped on the drop targets but if one returns to initial start point (due to having another drag object being dropped on and the one in place being reset) you cannot change the state of the drag object back to normal.
Basically what is needed is either to be able to reset state to normal when not dropped on a target OR a trigger which recognizes that a drop object is in use. So we can trigger the submit button to disappear again when the object is NOT IN USE.
2016 Now, this should be basic drag and drop functionality to ensure users can actually only submit an answer, when an answer is actually given, not just floating around or back in it's usual starting point.
Now we are facing this problem in Articulate Storyline 3. Please give a solution for this problem.
Hi Aiswarya! I'm happy to dig into this with you. Can you tell me more about the problem you're facing? Are you trying to design a drag-and-drop quiz slide?
If you're able to share a sample file with a slide or two, that would be super helpful!
Hi,
In free form drag and drop template, first we dropped the object to any of
the target position then we again drop the another object on top of the
first object. At that time the first object return to its initial location
but its state not return to the normal, it is continuing in dropped state
or drop correct or drop incorrect state. Because of this we cannot identify
the player filled all the drop target locations. Can you help me to solve
this problem.
We are using the Articulate Storyline 3.
Hi there, Aiswarya. Thanks for giving some detail about what's happening in your file. I made a 2 minute Peek screencast to show how the drop states should work in Storyline 3.
When you drag and drop an item on a target, you should immediately see the Correct or Incorrect state. If you drop another item on the same target, you should see the first item move back to its original position, and return to a normal state.
If you manually drag an item back to it's starting location, however, it's considered a "drag-and-drop," and you'll see the Drop Incorrect state.
Let me know what's happening in your file! If you can share some screenshots of your setup, or better yet, an example .story file, that would be so helpful. Use this link if you need to keep it private. Thanks!
@Crystal Horn
Your screencast shows how it's supposed to work, which Storyline version were you using? Could you share your test file to see if it behaves the same on my machine?
I tried 3.3.1, 3.4.1, 3.5.1, and the current Storyline 360 version - none of them reset the state of the swapped out drag item :(
Hi there, Jasmin. I was using Storyline 3 update 5 in the above example. I don't have the same source file, but here's a new one with the same setup described above.
What are you seeing on your end? If you'd like to share a screencast or your .story file, I'm happy to have a look! You can share your file publicly here or privately using this link. I'll delete it when I'm done troubleshooting.
More than 3 years and I'm facing the same issues like Lewis described... I know, there is a solution where I have to use a hugh amount of triggers. However, an interaction as essential as "drag and drop" should work without such errors. So: Is there any update regarding this problem?
Thanks for any help.
Hi Stefan,
Thanks for contacting us and sharing that you are running into a similar challenge.
This has been reported to our team and this conversation is attached so that any updates can be shared with you here.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
It's been five years and still no resolution here?
I have this same issue - the object's state does not go back to NORMAL state upon kicked from the target point where another item is dragged to the target point which has already a dropped item. I used variables and state triggers for dragged and dropped objects to debug but still cannot solve this one. I hope Storyline360 should check this drag and drop 'state' issue.
I'm having the same issue. I've tried all kinds of triggers and variables, to no avail. This really needs to be an essential feature, as other users have mentioned. I'm posting here, because I'm hoping that the more users that post about this, the more likely it will be fixed.
I concurr. I've wresteled with the same issue without a decent workaround. I agree with all that have said this should be an essential feature. Several comments over the years should warrant immediate attention.