I am not sure what happened. But my storyline file has a glitch in it.
In this drag and drop exercise you're supposed to stack the blocks on a base block. Once the base block is filled then you can stack the block on top of the next block. Before the update, users would not be allowed to stack blocks outside of their assigned column.
However now users can stack the blocks all willnilly.
Any idea on how I can fix this or what setting I'm missing... I've attached a video of the file in action.
Sorry to hear you've run into this setback. Thanks for sharing your .story file!
Testing the behavior on my end (64-bit Storyline 360 version 3.84.31722.0 via Windows Parallels on a Mac M1) I was able to reproduce the same issue. After rolling back to 64-bit Storyline 360 version 3.82.31354.0 the behavior could not be observed.
Our development team is tracking a known bug causing Drag-and-Drop interactions to work even if the drop target state is cleared of all objects.
I've linked this discussion to the bug report and will provide updates as soon as a fix is in place. In the meantime, as a workaround, we suggest reverting back to Storyline 360 version 3.82.31354.0 or earlier, where the bug is not present.
Thank you for your patience. Sorry if this has been slowing you down!
4 Replies
It’s a lot easier to make fix-it suggestions if we can take a look at the .story file. Attach it here.
Sure here you go
Hi LiG Playmakers Designer!
Sorry to hear you've run into this setback. Thanks for sharing your .story file!
Testing the behavior on my end (64-bit Storyline 360 version 3.84.31722.0 via Windows Parallels on a Mac M1) I was able to reproduce the same issue. After rolling back to 64-bit Storyline 360 version 3.82.31354.0 the behavior could not be observed.
Our development team is tracking a known bug causing Drag-and-Drop interactions to work even if the drop target state is cleared of all objects.
I've linked this discussion to the bug report and will provide updates as soon as a fix is in place. In the meantime, as a workaround, we suggest reverting back to Storyline 360 version 3.82.31354.0 or earlier, where the bug is not present.
Thank you for your patience. Sorry if this has been slowing you down!
Thanks or letting me know!