Our team has been using these drag and drop routines for years with Storyline 1 and 2 with no issue. Using Storyline 360, the hover state will remain after the drag button jumps back. This occurs in IE and Edge; Chrome works fine. It happens in both Modern and Classic players.
I'd submit a support ticket. It looks like the button is stuck in the down state until it's clicked (almost acting like a selected state)
On a side note, instead of disabled, you could use a drop correct state which is one of the built in states. In fact, I'd use the convert to freeform feature to build the drag/drop and you wouldn't need to use the triggers.
Of course, it all depends on your real project needs as this was just a demo slide.
I tested using Drop Correct instead of Disabled and it still had the same issue.
And yes, it would be simpler to use the buit-in freeform routine, but our standard is not to use the Submit button so the user gets instant feedback on a correct drop.
I'm assuming it has something to do with MS browsers handling it differently since it still works fine on Chrome, but I will submit a ticket.
You can use the freeform without a submit button, the freeform also gives more options than using the drag triggers. For every drag and drop i always use a freeform, as it offers more flexibility with the automatic state changes.
In my attached example I do use freeform for some of the functionality. The only added trigger I have is to make it so the dragged button cannot be clicked on/moved once it is dropped on a correct target. Any other state would not allow this... although maybe a mask could be used to cover the button, but that's gets needlessly complicated.
Either way, the intent of my original post was to point out the hover state sticking issue, which happens no matter what state is used once the button is dropped. It is when the button jumps back from an incorrect target.
Thanks for bringing me back around to the issue you were reporting Casey :)
I appreciate you sharing a demo file for me to take a look at as well. I took a look and mimicked the behavior you shared in your recording, but I'm not seeing the same behavior. Here's my recording.
9 Replies
I'd submit a support ticket. It looks like the button is stuck in the down state until it's clicked (almost acting like a selected state)
On a side note, instead of disabled, you could use a drop correct state which is one of the built in states. In fact, I'd use the convert to freeform feature to build the drag/drop and you wouldn't need to use the triggers.
Of course, it all depends on your real project needs as this was just a demo slide.
Here's a quick tutorial for those interested in using the convert to freeform for the drag and drop interaction.
Thank you for the response Tom.
I tested using Drop Correct instead of Disabled and it still had the same issue.
And yes, it would be simpler to use the buit-in freeform routine, but our standard is not to use the Submit button so the user gets instant feedback on a correct drop.
I'm assuming it has something to do with MS browsers handling it differently since it still works fine on Chrome, but I will submit a ticket.
Thanks!
You can use the freeform without a submit button, the freeform also gives more options than using the drag triggers. For every drag and drop i always use a freeform, as it offers more flexibility with the automatic state changes.
Hi Casey,
Looks like the example Tom shared provides a solution without the Submit button and with instant feedback :)
In my attached example I do use freeform for some of the functionality.
The only added trigger I have is to make it so the dragged button cannot be clicked on/moved once it is dropped on a correct target. Any other state would not allow this... although maybe a mask could be used to cover the button, but that's gets needlessly complicated.
Either way, the intent of my original post was to point out the hover state sticking issue, which happens no matter what state is used once the button is dropped. It is when the button jumps back from an incorrect target.
Thanks!
Thanks for bringing me back around to the issue you were reporting Casey :)
I appreciate you sharing a demo file for me to take a look at as well. I took a look and mimicked the behavior you shared in your recording, but I'm not seeing the same behavior. Here's my recording.
Even when publishing it looks great to me.
I'm using the latest update, which is Update 17.
It is definitely doing it for me. I even tried rebuilding it and it does it in IE 11 every time.
Sent from my iPhone
Thanks for the update Phil, let me take a look in IE11 specifically.
That was it. I'll get this issue reported. Thanks again for chiming in Phil!
This discussion is closed. You can start a new discussion or contact Articulate Support.