Simple keyboard trigger doesn't work

May 21, 2015

I have a simple Home screen with 8 buttons. Each button jumps to a sub-screen. The sub-screens are all based on a master slide. The master has a X button that jumps back Home. I also added triggers to Home so, if you hold down Ctrl and press a number 1 through 8, it jumps to the sub-screen. So far so good.

However, when a user is in one of the sub-screens, I want him to be able to press Ctrl/Q or some other key combination and jump back home. It seems simple and straightforward but it won’t work. I’ve tried putting the Ctrl/Q trigger in the master. Then I took it out of there and tried it in each of the sub-screens. I’ve tried different letters to replace Ctrl/Q (letters that have no special function). No luck. Does anyone have suggestions why this won’t work?

This is the updated version of SL2.

12 Replies
Ashley Terwilliger-Pollard

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. 

Karel Wagner

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. 

Ashley Terwilliger-Pollard

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.

Ashley Terwilliger-Pollard

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. 

This discussion is closed. You can start a new discussion or contact Articulate Support.