Hey all. I have a series of screenshots that I've added in Test mode from a video. Each screen has a hotspot on it, but I want the cursor NOT to change into a hand when it's hovered over.
I've right-clicked on each hotspot and turned off the "Show hand cursor on hover" option, but when I run the lesson, the hand still changes into a cursor on hover. Any ideas?
Hello! Any update on this issue in 360? I have v3.60.26947.0. The workarounds suggested in this thread DO remove the hand on hover, however we elected to remove the Submit button completely. Applying temp workarounds with many large files is not feasible at this time.
Hello. Same issue here. Using v3.61.27106.0. Recorded my screen to create 50 or 60 slides with hotspots in a quiz environment and all of the hotspots show the hand cursor upon hover even though the setting is turned off.
I have placed few hotspots on the .mp4 video and at the end of the video learner need to hover the mouse to view the additional information. But hand cursor is not working in this situation.
I notice this concern was mentioned 7 years ago. However, I don't see where I have the ability to turn off that feature. I don't want the hand to show at hover, but the option that shows when I right click on the hotspot is to turn it on. It does it whether the feature is checked or not.
Has there been a solution? I'm using hot spots in a try me interaction and I don't want the users to see the hand over the hotspot for the correct answer.
Sorry to hear that you ran into this issue. I tried testing this behavior using the latest version of Storyline 360 but I was unable to replicate it. Here's a quick recording of what I'm seeing when hovering over hotspots generated by a screen recording. Can I ask if you are working out of the latest version of Storyline 360?
If you are, please share a copy of your project file here or in private by opening a support case so I can take a look at why we're getting different results. We'll delete it when we're done testing!
32 Replies
Hello! Any update on this issue in 360? I have v3.60.26947.0. The workarounds suggested in this thread DO remove the hand on hover, however we elected to remove the Submit button completely. Applying temp workarounds with many large files is not feasible at this time.
Hi Jill,
Thanks for checking in and sharing that you're having the same issue.
We don't have an ETA at this time, but we'll pop in and share any updates with you here as soon as it's available.
Hello. Same issue here. Using v3.61.27106.0. Recorded my screen to create 50 or 60 slides with hotspots in a quiz environment and all of the hotspots show the hand cursor upon hover even though the setting is turned off.
Hello Team,
I have placed few hotspots on the .mp4 video and at the end of the video learner need to hover the mouse to view the additional information. But hand cursor is not working in this situation.
Could you please provide any solution on this?
Regards,
Hi, Dipu.
Thank you for reaching out!
When you say the "hand cursor is not working in this situation", do you mean the hover is not showing, or the cursor is not changing?
The cursor will only change if you have a trigger connected to "When the user clicks".
I hope this helps!
Hi,
I notice this concern was mentioned 7 years ago. However, I don't see where I have the ability to turn off that feature. I don't want the hand to show at hover, but the option that shows when I right click on the hotspot is to turn it on. It does it whether the feature is checked or not.
Has there been a solution? I'm using hot spots in a try me interaction and I don't want the users to see the hand over the hotspot for the correct answer.
Hi Karel,
Sorry to hear that you ran into this issue. I tried testing this behavior using the latest version of Storyline 360 but I was unable to replicate it. Here's a quick recording of what I'm seeing when hovering over hotspots generated by a screen recording. Can I ask if you are working out of the latest version of Storyline 360?
If you are, please share a copy of your project file here or in private by opening a support case so I can take a look at why we're getting different results. We'll delete it when we're done testing!