Simple keyboard trigger doesn't work

Hi John,

Some keyboard clicks are associated with web browser set ups as detailed here. 

Personally I would stay clear of CTRL functions as they already have functions in both windows and mac. Use keys like NUMPAD or alt+x as these are more likely to be safe function key choices.

Using ALT seemed like a good idea but, unfortunately, it doesn't seem to work. I changed all the triggers. I tried previewing  the entire project and I also tried publishing and pressing the "View Project" button. When I press ALT plus another key, nothing happens. Bummer!

Does anyone have suggestions?

I found this page that that has a comparison table of all browser keyboard shortcuts. No browser uses a combination of Ctrl plus any of the numbers except 9 and 0.  I tried that and it doesn't work either. I'm starting to wonder whether Storyline responds to key combinations.

Hi John, 

Storyline does allow for key combinations or key press triggers - but using the CTRL key can be problematic - could you look at just using a number or letter vs. including the CTRL key? You'll also want to make sure you're testing this in the intended publish environment and browser to ensure it all works as expected. 

Ashley - thanks for your suggestions.

I created triggers that use the Alt key combined with a number on the numeric keypad to jump to the various pages. I published it for web and posted as a Moodle Resource. The keyboard commands don't do anything.

Can you (or anyone) think of anything else for me to try?

Hi John,

I can't think of anything else right now but I'll defer to the community and hopefully they'll be more creative! 

Hi Everyone, 

I'm building a simulation (because Storyline2 will not capture a screen by screen recording of this application) in which the user must press 'Page Down' several times.

I've added the trigger 'Jump to x screen when user press the 'Page Down' key, however, it will not advance. Any ideas? 

I've attached a screen shot of my trigger. 

Thanks Karel for sharing that image here. We've recently reported an issue to our team where the key press triggers aren't working as expected in the Flash output. I don't have an update to share at this time or a timeframe to offer in regards to when I'll hear back from our QA team, but in the meantime I'd suggest looking into the following workarounds:

• Direct the user to the HTML5 output by pointing to the story_html5 file (if hosting in an LMS you may need to reach out to them for directions on how to point directly to it) or have the user disable Flash and access the course in one of the browsers supported here. 
• Having the user click on the slide seems to bring the focus back to allow for key press triggers to work
• Instead of assigning these triggers to the player navigation buttons, it seems that using custom navigation (your own buttons on the slide itself) allows these to work better. 

I'll include this thread with the report file with our team so that we can keep you posted here with any updates.

Thanks Ashley,

I take comfort in knowing it is not me. I put a virtual keyboard on the slide and instructed users to click the 'Page Down' key from there. It's not ideal, but it will do for now. Thanks for the information on the trigger issue.

Thanks for the update Karel and we'll keep you posted here with any additional information. 

Hi Karel,

The issue that we discussed in regards to the key press triggers not working in the Flash output has been fixed in Update 7 for Articulate Storyline 2. Install the latest version of Storyline 2 to take advantage of the new features and fixes, then republish your course. With this fix, you'll want to ensure you're using a key press trigger or a click trigger on the object, not both of those triggers on the same object. 

If you're still having issues with your course, please feel free to let us know here or by reaching out to our Support Engineers here.