I'm working on a software simulation. The user needs to enter info using all uppercase letters. So as a first step, I have them press the Caps Lock key. I've set up a trigger that should advance to the next slide when the user presses the Caps Lock key. This works fine in preview mode, but it doesn't work when published for the Web or an LMS. I'd greatly appreciate any assistance the community is able to provide.
Thanks, Lynn. I uploaded it here to Review to give it a quick test, and it looks like I was able to use the caps lock key to advance. Can you give that a test for me?
I wasn't sure if you were using Storyline 3 or 360, but you could also test by uploading content to SCORM Cloud for LMS testing and/or Tempshare for web testing.
Thanks for taking a look at it. I'm using 360, which was one of the ways I tested it. I also tested it on our LMS. Caps Lock didn't work in either place. It also didn't work in the versions you uploaded. I thought it might be a problem that was specific to my computer, but I had a co-worker test it with the same results.
That Review link did allow me to use the Caps lock to advance to the next slide. Can you tell me what browser you're viewing it in? Do you know if you have Flash enabled or not?
Thanks so much for sticking with us on this! We've done some further testing, and we found that pressing the Caps Lock key to advance to the next slide doesn't work unless the learner first clicks on the slide itself. Essentially clicking the player Next button is taking the focus away from the slide.
If you click on the slide before pressing Caps Lock, you'll be able to advance to the next slide. Also, if you place a button on the previous slide and use that to jump to the Caps Lock slide (instead of the player Next button), the Caps Lock keypress trigger will work correctly.
Will the workaround of using a button on the previous slide to jump to the Caps Lock slide work for now? I'll tag this discussion to be updated with any changes on this behavior. Sorry if it's slowing you down!
Absolutely! Simply click here to open the forum discussion, then click the Edit link below your post. That will allow you to remove your file attachments.
16 Replies
Hi Lynn,
I'd love to take a look at your file and see how this is set up. Can you share a copy of your .story file with us here?
Thanks for getting back to me. I've attached the file. Slide 1.5 has the trigger to advance to the next slide when the user presses the Caps Lock key.
Thanks, Lynn. I uploaded it here to Review to give it a quick test, and it looks like I was able to use the caps lock key to advance. Can you give that a test for me?
I wasn't sure if you were using Storyline 3 or 360, but you could also test by uploading content to SCORM Cloud for LMS testing and/or Tempshare for web testing.
Thanks for taking a look at it. I'm using 360, which was one of the ways I tested it. I also tested it on our LMS. Caps Lock didn't work in either place. It also didn't work in the versions you uploaded. I thought it might be a problem that was specific to my computer, but I had a co-worker test it with the same results.
Hi Lynn,
That Review link did allow me to use the Caps lock to advance to the next slide. Can you tell me what browser you're viewing it in? Do you know if you have Flash enabled or not?
I'm using Chrome and Flash is enabled.
Hi there Lynn,
Thanks so much for sticking with us on this! We've done some further testing, and we found that pressing the Caps Lock key to advance to the next slide doesn't work unless the learner first clicks on the slide itself. Essentially clicking the player Next button is taking the focus away from the slide.
If you click on the slide before pressing Caps Lock, you'll be able to advance to the next slide. Also, if you place a button on the previous slide and use that to jump to the Caps Lock slide (instead of the player Next button), the Caps Lock keypress trigger will work correctly.
Will the workaround of using a button on the previous slide to jump to the Caps Lock slide work for now? I'll tag this discussion to be updated with any changes on this behavior. Sorry if it's slowing you down!
Thank you for taking a look at this. The e-learning heroes community is just awesome. I really appreciate you coming up with a workaround.
This is a trigger I'd like to be able to use in the future. It would be great if a fix was developed for this.
I'm happy we could find a workaround, Lynn! We'll keep you posted on a news of a fix.
Thanks much, I appreciate your help. I'd like to remove the attached files from this post. Is that possible?
Absolutely! Simply click here to open the forum discussion, then click the Edit link below your post. That will allow you to remove your file attachments.
Thanks. Would it be possible to delete the file you attached?
Sure thing! The files have been removed. 😊
Thank you.
I think I had a link as well in my reply, Lynn - so I deleted that too.
Thanks much.
This discussion is closed. You can start a new discussion or contact Articulate Support.