Forum Discussion
Flummoxed by Drag-and-Drop Tester Issue
I created a drag-and-drop interaction for a course that is currently being tested. Out of 10 testers, only 1 had an issue with it that I am unable to figure out (or even re-create).
My triggers and variables make it so that the "next" button does not reappear until all of the layers have been viewed. (Layers appear when the user drops a correct object on the target.)
For one tester, even though all of the correct choices are on the target, the "next" button never reappears:
Neither I nor any of the other testers experienced this issue, and none of us can re-create it, no matter how hard we try to break it. I have checked everything I know to check, but I still can't figure it out.
If anyone has any insight, I would be much obliged!
-Nicki
3 Replies
Hi Nicki,
I believe you can "break" your project by simply closing out the appearing layers fast. Note that your triggers for adjusting the "drag" values are based on "when the timeline ends on this layer." By quickly closing out the layer with the hotspot, the "drag" variable is never adjusted to "True" because the layer never reaches the end of the timeline and thus the "Next" button never appears. On the contrary, if I take my time and allow the layers to remain open for a few seconds, the Next button appears after viewing all the layers.
I suggest moving the Oval Hotspot, and the X underneath it, that closes the layer to not appear and be available until after the variable has been triggered. You could achieve this by putting a cue on the timeline of the layers, say 1 second in, and then readjusting your triggers to adjust the "drag" variables when the timeline reaches the cue point, not when they reach the end of the layer. Then, later in the timeline, say 2 seconds in, you could have the X and Oval hotspot appear to allow the user to close the layer.
If this solves your problem, please mark this answer as the solution. Otherwise, feel free to ask a follow-up question.
I tried breaking it this way, but was unable to. It still worked fine even if I closed the layer immediately.
UPDATE: We determined that the issue only occurs in the LMS and not in Storyline Review. Is there any reason this would work in review but not in an LMS?
