We are creating a 'what am I' interaction where users read a description and need to choose the correct key on the keyboard. On one slide, the correct key is the tab key. However, when trying to choose the tab key as the correct key in form view, it is not registering and just moving to the next point (like tab would normally do!) Could anyone help with a way around this please.
The Tab key functions as an accessibility feature for screen readers. You can turn off that functionality in the Size and Position window, but the tab key will still cycle through objects on the slide from the upper-left corner to the lower-right corner. Could you use another key instead of Tab?
Tell me more about what's going on with Alt + F. Are you using this keystroke in Storyline Preview or after publishing?
We've found that Storyline doesn't detect the Pause Break key. What function are you trying to perform with that key? There might be another keyboard shortcut I can recommend.
We are creating an interaction relating to a system which uses keys such as pause break, tab, alt &F7 and F10. We are showing a description on screen and the user is to hit the correct key on the keyboard for the description. I am considering some alternatives to offer, but the sponsor is keen to use this interaction.
Hey Matthew. Would you happen to know of any way to prevent the browser from executing keys that are pressed in a Storyline published project? Ctrl+W for example will close the browser window. Is there a way to trap that keypress and prevent the browser from interpreting it and executing it? Thanks for any insight you might have on this.
Thanks Matthew! I gave that a quick try using the code plus the line of code for the story_html5.html file. It didn't work for the Ctrl+W key in Chrome, Brave, FireFox as it closed the browser window when pressed. Looks like I'll need to dig a little deeper to see if I can trap that key combo.
As I was testing, I noticed if a user were to exit the course during the on-screen demo that uses this javascript and select resume where left off, the javascript no longer seems to work and the user gets stuck on a slide. It works fine if you go all the way through and don't stop to exit. Does it lose connection with the javascript on resume?
Thanks for the response. I am a novice javascript user. My approach is going to be to create a true/false variable for isSlideStarted. Two triggers for true if slide starts; false for slide end so I can use on multiple slides? Fingers crossed.
11 Replies
I also have a similar issue with alt plus f keys not recognising when previewing and the pause break key not being recognised at all.
Any help will be appreciated!
Many thanks
Chris
Hey, Chris!
The Tab key functions as an accessibility feature for screen readers. You can turn off that functionality in the Size and Position window, but the tab key will still cycle through objects on the slide from the upper-left corner to the lower-right corner. Could you use another key instead of Tab?
Tell me more about what's going on with Alt + F. Are you using this keystroke in Storyline Preview or after publishing?
We've found that Storyline doesn't detect the Pause Break key. What function are you trying to perform with that key? There might be another keyboard shortcut I can recommend.
Hi Alyssa
We are creating an interaction relating to a system which uses keys such as pause break, tab, alt &F7 and F10. We are showing a description on screen and the user is to hit the correct key on the keyboard for the description. I am considering some alternatives to offer, but the sponsor is keen to use this interaction.
Many thanks
Chris
Hi Matthew
It seems that this will do the job - Thank you!
The only exception is the key required is Alt & F7 - apologies, after reading my original post, I did not make this clear!
If you could please share the .story file it would be appreciated
Many thanks
Chris
Thanks for jumping in to assist here, Matthew!
Thanks for this Matthew
I have never delved in the realms of Java script, but will be giving this a try!
Many thanks
Chris
Hey Matthew. Would you happen to know of any way to prevent the browser from executing keys that are pressed in a Storyline published project? Ctrl+W for example will close the browser window. Is there a way to trap that keypress and prevent the browser from interpreting it and executing it? Thanks for any insight you might have on this.
Thanks Matthew! I gave that a quick try using the code plus the line of code for the story_html5.html file. It didn't work for the Ctrl+W key in Chrome, Brave, FireFox as it closed the browser window when pressed. Looks like I'll need to dig a little deeper to see if I can trap that key combo.
This worked for me! Thanks! Where does the 'preso' id come from? Is it in the Storyline publish?
Hi Matthew,
As I was testing, I noticed if a user were to exit the course during the on-screen demo that uses this javascript and select resume where left off, the javascript no longer seems to work and the user gets stuck on a slide. It works fine if you go all the way through and don't stop to exit. Does it lose connection with the javascript on resume?
Thanks for the response. I am a novice javascript user. My approach is going to be to create a true/false variable for isSlideStarted. Two triggers for true if slide starts; false for slide end so I can use on multiple slides? Fingers crossed.