Forum Discussion
Storyline: Hand cursor during shape hover - Can I stop this?
This question was actually asked before on this thread:
http://community.articulate.com/forums/p/23419/236620.aspx
But was not answered because the question was unclear....although it made sense to me!
Here's the scenario: I've set up a freeform pick many quiz like Jeanette posted here:
Jeanette set this up using shapes with states rather than hotspots! I know that with a hotspot, you can turn off "Show hand cursor on hover", but I'm wondering if you can replicate this with a shape state?
If I right click on my shape, I don't get the hand cursor option, so I was wondering if there was any other work around.
In my pick many quiz scenario I don't want the user to just hover around the image to find the hand cursors and pick those areas. I'd like to turn off the hand cursor if possible.
I hope this makes sense!
I really appreciate any feedback!!
~Amber 
33 Replies
I have a similar issue. The attached is a quiz question with 49 errors on a form. The client wants to test a person's ability to find them all. I first tried hotspots but found that hotspots would be accepted on submit as correct answers. Next I drew ovals and set them to invisible in normal with a state change on selecting. So far so good, now the client says on hover the cursor changes from pointer to hand and serves to hint that the active oval is a error location. How to prevent the cursor change?
Hi John! That certainly looks like a tough quiz question! Here are a few tips I'd like to share:
- Add an "invisible" rectangle to cover the entire slide, and place it behind the 49 ovals on the slide. Then, add that rectangle in Form View as an answer choice, but don't check it as correct. In essence, clicking anywhere in the rectangle would be incorrect.
- You may also want to add a "selected" state to each of the ovals, perhaps with a colored outline. This will help learners to know which ovals they have already selected, since it can be challenging to keep track of 49 different objects.
I hope those suggestions will work for your design!
Hi Alyssa,
Yup, I had the selected states defined already.
Eureka! Your solution is brilliant, although I do not understand why it works, since the invisible rectangle is behind the selection ovals.
Thanks so much, you saved my bacon.
Best Regards,
John Fritts
Instructional Designer | QMS Technical Training | Human Resources - AMIE
Office: 239-598-4302 x71162
Mobile: 480-352-7199
Email: John.Fritts@Arthrex.comThis e-mail and any files transmitted with it are the property of Arthrex, Inc. and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender at 239-643-5553 and delete this message immediately from your computer. Any other use, retention, dissemination forwarding, printing or copying of this e-mail is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, while Arthrex uses virus protection, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Hey John! We're happy to help. Just a little note - your contact information from your email signature is included when you reply via email. You can click here to edit it out.
What you should see with Alyssa's trick is that the hand cursor doesn't go away, since the entire area is a "clickable" answer. Now, there isn't any discerning between the empty space and the actual error fields.
Hey John, happy I could help!
It works because you added an additional "incorrect" option to the form view. In other words, the large rectangle is clickable so a hand mouse cursor will appear, but it isn't the right answer.
By the way, replying via email includes your signature with contact information in the public forum. Feel free to edit your reply here!
Sorry to bring this up again, but I need the opposite to work. I have 8 boxes as hotspots on 8 different slides; each box represents the answer on a different slide. Right now, the cursor is a finger over the entire thing, even where there is no clickable hotspot. How can I set the interaction to only allow clicks where there exists a hotspot? I remember Captivate having this kind of capability, so surely Storyline 3 does as well....
Hi Ross!
I see that Tom is helping you in this discussion! We'll keep the conversation going in that thread.
adding on to Lauren's question.. would you be able to share a .story file here that has this problem with the hand cursor?
Hi Brian,
The hand cursor appears for me when I have a trigger linked to an object that I then hover over.
Can you try doing a repair of your Storyline 360 installation to see if this helps? Let me know if this works for you!
Went through the repair sequence for Storyline 360 and it's still behaving the same way for me. I've attached the .story file, let me know if you have the same experience with it or if it works for you, as well as if I'm doing something incorrectly.
Hi Brian,
Thanks for sharing your project file. I can see that you already had the 'Show Hand Cursor on Hover' enabled for your hotspot. I checked our bug list and saw that we are tracking a known issue which prevents the cursor from changing to a hand icon when hovered over a hotspot. I went ahead and added this support case to the bug report so we can notify you as soon as a fix is released. Thanks for raising this, and we're sorry for any inconvenience the bug may have caused.
Thank you!
Hi I know this is a very old thread, but I seem to be having the same issue. I added a hot spot (no triggers) behind my invisible shapes in order to have hand cursor for entire slide but it doesn't seem to be working. Can anyone assist? Thank you!
Hello Jessica,
The bug discussed in this thread is still open, but I've added your voice to the report so we can track its impact. We'll let everyone subscribed to this thread know as soon as a fix is released.
