I want to have the setting 'Return item to start point if dropped outside a correct drop target' AND Drag Over state for every drop target available, even if this is not a correct drop target for the dragged item.
It does not work even if we add the drop targets a second time with matching '(None)' drag item.
This option is not really useful if it shows the learner only the correct option... I also need a visual feedback to help the learner understand where he dropped the drag item as the drop targets are really close one form another.
Thanks for letting me take a peek at your file! It looks like we've got a bug with the "Drag Over" state. This state doesn't work if you're using the "Return item to start point if dropped outside - a correct drop target" setting.
To work around this bug, you can use the "Return item to start point if dropped outside - any drop target" setting.
I'll bring this up to our Product team so we can get more eyes on this bug. If I get an update, I'll pass it along to you!
Thanks for your suggestion, but I don't want to do another work around here. Of course I can do that work around. But this is not the behaviour I want. I wanted a direct feedback, easy to understand for the learner and easy to implement as I have more than one drag&drop to do for this project. I don't want to add 'incorrect dropped state' and so on for all my objects so my learner can have this kind of feedback.
Good morning, Joyce! Appreciate you checking in, and sorry you're still at this obstacle.
I don't have an update on this issue as of yet, but I promise to keep you updated as soon as new information is available. Here's a glimpse into how we tackle bugs.
While we continue to investigate this bug, we're happy to have a look at your project to explore any other custom approaches. If you're able to share the .story file, please use this private upload link. We'll let you know what we find and will delete the file after.
I'm still trying to do the same basic drag&drop action and it's still not working...
As I said, I know I can use a workaround, but it would be nicer to have something working as it should...
It works with the "Return item to start point if dropped outiside any drop target" but not with the "Return item to start point if dropped outiside a correct drop target". I don't understand what is so hard to implement and why it's not fixed yet 7 months later.
Sorry, this has been frustrating! You're correct, the workaround for this bug is to use the "Return item to start point if dropped outside - any drop target" setting instead.
The bug has been reported to our team, but based on the limited impact and viable workaround, it's still an open issue for investigation. I'll let the team know you reached out again, and if there is any change in the status of this one, I'll keep you posted.
Let me report this as a potential bug to our team so we can take a closer look. I appreciate you bringing this up, and will update this discussion on any new developments!
I'm finding myself having this exact problem and have been very frustrated (and have wasted my employer a lot of money who has had to pay me for messing with this issue--so annoying).
I was wondering what work-around, if any, you have built for this? I have built about 400 triggers to make a drag and drop interaction work the way I need it to with various drag over states but the fact that the drag item will not bounce back to it's starting point if not dropped on it's correct target is a huge problem. And honestly, it seems ridiculous that something so simple can't work how it says it's supposed to.
Hi Nina, and welcome to the E-Learning Heroes community! ✨
I apologize for the frustration you are having with your drag and drop interaction not working as expected.
To clarify, the bug we are tracking involves the Drag Over state. This state doesn't work if you're using the "Return item to start point if dropped outside - a correct drop target" setting.
The current workaround for this bug is to use the "Return item to start point if dropped outside - any drop target" setting.
Let me know if that matches your experience, or if there's something else I can help you with.
I can also link you to receive updates on the bug if anything changes.
I have great news to share! We are no longer seeing this bug in our latest version of Storyline 360 (Build 3.72.29699.0), where when a caption is rotated, it is no longer recognized as a drag or drop target.
To make sure your software is up-to-date, please launch the Articulate 360 desktop app on your computer and select the Update button next to Storyline 360. I've included our step-by-step instructions here!
11 Replies
Hi Joyce,
Thanks for letting me take a peek at your file! It looks like we've got a bug with the "Drag Over" state. This state doesn't work if you're using the "Return item to start point if dropped outside - a correct drop target" setting.
To work around this bug, you can use the "Return item to start point if dropped outside - any drop target" setting.
I'll bring this up to our Product team so we can get more eyes on this bug. If I get an update, I'll pass it along to you!
Hi Alyssa,
Thanks for having a look on my case.
Thanks for your suggestion, but I don't want to do another work around here. Of course I can do that work around. But this is not the behaviour I want. I wanted a direct feedback, easy to understand for the learner and easy to implement as I have more than one drag&drop to do for this project. I don't want to add 'incorrect dropped state' and so on for all my objects so my learner can have this kind of feedback.
Yes, please, keep me in touch about this bug.
Hello Alyssa,
Any news about this bug? I'm facing the same issue again where I have to do a workaround which itself is adding more not user-friendly issues...
Can you please move forward on this problem?
Best regards,
Good morning, Joyce! Appreciate you checking in, and sorry you're still at this obstacle.
I don't have an update on this issue as of yet, but I promise to keep you updated as soon as new information is available. Here's a glimpse into how we tackle bugs.
While we continue to investigate this bug, we're happy to have a look at your project to explore any other custom approaches. If you're able to share the .story file, please use this private upload link. We'll let you know what we find and will delete the file after.
Well...
I'm still trying to do the same basic drag&drop action and it's still not working...
As I said, I know I can use a workaround, but it would be nicer to have something working as it should...
It works with the "Return item to start point if dropped outiside any drop target" but not with the "Return item to start point if dropped outiside a correct drop target". I don't understand what is so hard to implement and why it's not fixed yet 7 months later.
Hello Joyce!
Sorry, this has been frustrating! You're correct, the workaround for this bug is to use the "Return item to start point if dropped outside - any drop target" setting instead.
The bug has been reported to our team, but based on the limited impact and viable workaround, it's still an open issue for investigation. I'll let the team know you reached out again, and if there is any change in the status of this one, I'll keep you posted.
I have noticed another "bug" possibly - that when I rotated a caption (actually flipped it vertically) it stopped acting as a valid drop object.
Flipped the caption back and it worked fine. Mapping issue with the caption co-ordinates?
Hi there, Ian!
I'm seeing the same problem in Storyline 360 Update 39 and Storyline 3 Update 9:
Let me report this as a potential bug to our team so we can take a closer look. I appreciate you bringing this up, and will update this discussion on any new developments!
Hi Joyce!
I'm finding myself having this exact problem and have been very frustrated (and have wasted my employer a lot of money who has had to pay me for messing with this issue--so annoying).
I was wondering what work-around, if any, you have built for this? I have built about 400 triggers to make a drag and drop interaction work the way I need it to with various drag over states but the fact that the drag item will not bounce back to it's starting point if not dropped on it's correct target is a huge problem. And honestly, it seems ridiculous that something so simple can't work how it says it's supposed to.
Hi Nina, and welcome to the E-Learning Heroes community! ✨
I apologize for the frustration you are having with your drag and drop interaction not working as expected.
To clarify, the bug we are tracking involves the Drag Over state. This state doesn't work if you're using the "Return item to start point if dropped outside - a correct drop target" setting.
The current workaround for this bug is to use the "Return item to start point if dropped outside - any drop target" setting.
Let me know if that matches your experience, or if there's something else I can help you with.
I can also link you to receive updates on the bug if anything changes.
Hi, everyone!
I have great news to share! We are no longer seeing this bug in our latest version of Storyline 360 (Build 3.72.29699.0), where when a caption is rotated, it is no longer recognized as a drag or drop target.
To make sure your software is up-to-date, please launch the Articulate 360 desktop app on your computer and select the Update button next to Storyline 360. I've included our step-by-step instructions here!