14 Replies
Ashley Terwilliger

Hi Jake and welcome to Heroes! 

You can add a shortcut key as a part of a trigger (advance to next slide) as I have done below here:

 If you're conducting the screen recording within Storyline, it should pick up the use of shortcut keys (for example, I tested it with CTRL+C to copy some text). If you are not satisfied with the way they display, you could look at placing markers throughout your recording that your viewers can roll over and click for more information, including which keystrokes to use? 

Here's how to add and edit markers in Storyline.  

Additionally, if you'd like to set this up as more of a quiz question - you could create a freeform question with the shortcut key as the answer as described here. 

Ashley Terwilliger

Hi Lisa,

I'm not sure if Jake is still subscribed here, as this thread is a bit older - I'm guessing you're using Storyline 2? Our QA team is aware of an issue in Storyline 2 currently where using the key press triggers does not allow the slide to advance unless the user has clicked on or brought the focus to the slide using the tab key or something similar. I'll include this thread in the report filed with our team so that I can provide any additional updates here once there is additional information to share. 

Ashley Terwilliger

Hi Lisa, 

The issue that we previously discussed in regards to the key press triggers not working as expected 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. 

CLP

Hello folks,

We are creating software tutorials that require key presses as well and finding that our key press triggers work fine locally and on ScormCloud when viewed with Chrome and Firefox, but not for IE8 through 11. As mentioned above by others, common chords like ctrl+c and F-keys get run within the browser itself. We are running/publishing with the latest build of SL2. The test file we are working with is attached. We would love to know if we are doing anything incorrectly with our triggers or publishing process, and if there is a solution that works with IE.

Thank you in advance

JB

 

Ashley Terwilliger

Hi JB,

Thanks for sharing the file here - and I see the same thing that you mentioned in regards to Chrome and Firefox working normally but IE11 triggering browser actions. There isn't anything I know of to change how one particular browser will react - so you may want to look at key presses that aren't associated with the browsers - typically the ALT, CTRL and Function keys are connected with the browsers so perhaps just alpha numeric keys?