Using a keyboard key as a trigger
Aug 30, 2015
I'm creating an interactive simulation using try mode. I have a screen recording and on one of the slides I have a Data Entry Box where I want the user to type a number from a list of options which show on the screen recording. Then then have to press a key on the keyboard to continue to the next slide.
I've set a variable on the data entry box to only accept the correct option number. I've put a button next to the data entry box with a trigger to jump to the next slide when the user clicks it. This works, but instead of using a mouse click I want to use one of the F keys on the keyboard (not the enter or tab key).
There's an option to do this in Adobe Captivate and it works. How can I do this in Storyline?
I'm using Google Chrome and it's not affected by the F keys. I've attached a sample file to show the set up.
9 Replies
I would avoid the function keys, I don't think you can test this in Storyline as F9 is publish.
It is probably easier to use a numeric question and set the submit key to F9, this is because using a data entry field for it to set the variable the control must lose focus this will not happen with a key command and as you have a condition it will not work.
Hi Phil
Thank for your reply. How do I add a numeric question to the slide when it's a screen recording?
I don't think you can you may be able to use the convert to freeform and use data entry as this will allow a key submit
I tried this, but the key I need to use is F12, which is used to publish in Storyline.
In Captivate when you add a Text Entry Box to a slide, it automatically adds a Submit Button with it.
Is there a way to view the code that's generated when adding data entry boxes and variables etc?
F12 in a browser will open the debug option, in Storyline you can add a submit button to the slide with the slide properties on the layer pane.
You can still use F12 but will not be able to test in preview and would need to publish either for CD or upload to a server for testing.
If you add a normal data entry than that is set to submit when the field loses focus and cannot change, you can fake a key entry but would need the control to lose focus if you need to use a condition.
You cannot view the code that is generated.
Hi Linda,
This looks similar to the discussion we had the other week, so I just wanted to connect the two and I'm glad Phil was able to weigh in and clarify some elements as well.
Can the keyboard short cuts be disabled in Storyline 2?
Hi Linda,
No you won't be able to disable the shortcuts for elements such as accessibility or the browser specific shortcuts while viewing the Storyline output. Also, here are the keyboard shortcuts that trigger specific functions while in Storyline.
Thanks John for sharing that update here - and I'm happy to hear Chrome will work for you. I suspect a number of users would agree with your statements about IE as well... ;)
This discussion is closed. You can start a new discussion or contact Articulate Support.