Using CTRL+X/CTRL+V to jump to a new slide - not working

Any suggestions for why this won't work? I've got one slide with CTRL+X and one with CTRL+V to do the same thing, but neither works. No other triggers (except next/prev buttons).

Here's the trigger panel

Thanks for whatever insight you can provide!

10 Replies

Leslie McKerchie
Staff

3 years ago04/20/16 at 5:40 pm (UTC)

Hi Holly!

It could be as simple as needing to adjust your Object on your Trigger to the actual slide or it could be a result of some of the following.

Some keystrokes are common keyboard shortcuts for web browsers—for example, F1, Alt+D, and Ctrl+T. Because learners view published courses in a web browser, some keystrokes could result in unwanted behavior. We recommend testing your published output before deploying it to ensure it works as you'd expect. You may need to adjust some of the keystroke requirements for your interactive elements if there's a browser conflict. See this article for more information.

There was also an update that addressed an issue, so be sure you're utilizing the latest update:

You may find that key-press triggers you've assigned to a slide don't work if you click the slide in your Flash output before invoking the key-press triggers. This issue was fixed in Update 7 for Articulate Storyline 2. See this article for details.

Holly MacDonald
Author

3 years ago04/20/16 at 6:16 pm (UTC)

Thanks Leslie - object is the slide and I'm on the latest update (Update 7).

I've removed the trigger for now, as we are up against a deadline, but would be interested to know if it's just something to avoid or if there's a workaround (with or without javascript).

Holly

Ashley Terwilliger
Staff

3 years ago04/20/16 at 8:37 pm (UTC)

Hi Holly,

What occurs when you try to use that trigger? Have you tested it in any other browsers to see if it's dependent on the browser? I know the common key press items such as CTRL V are typically reserved for the copy/paste/cut functionality - so that is likely what you're running into and if so I'd look at a different trigger set up or investigate workarounds such as Javascript which is not something we can offer support for, although the community is well versed in creating Javascript and may be able to weigh in here.

Holly MacDonald
Author

3 years ago04/20/16 at 9:55 pm (UTC)

Hi Ashley - the trigger does not fire, and we don't have much time to test so I've done something else instead, but will do some digging around javascript options when I have some more time to tinker.

Thanks!

Ashley Terwilliger
Staff

3 years ago04/21/16 at 1:01 pm (UTC)

Certainly understand Holly - and feel free to let us know if you need anything else.

Phil Mayor
Hero

3 years ago04/21/16 at 6:44 pm (UTC)

I don't think there is a solution for this ones the system will alway catch system commands.

Michael Hinze

3 years ago04/21/16 at 6:48 pm (UTC)

I agree with Phil, keyboard shortcuts that are used by the system or browser will always be 'caught' before they get to the Storyline content.

Holly MacDonald
Author

3 years ago04/21/16 at 6:49 pm (UTC)

Thanks Phil and Michael, will avoid them in the future...

Harish R

almost 2 years ago07/25/17 at 7:20 am (UTC)

This post was removed by the author

Harish R

almost 2 years ago07/25/17 at 8:06 am (UTC)

If Ctrl+S can be supported then why not Ctrl+C and Ctrl+V?

Leslie McKerchie
Staff

almost 2 years ago07/25/17 at 2:21 pm (UTC)

Hello Harish and welcome to E-Learning Heroes :)

As mentioned above, if the keystroke is used in a browser that will take precedence. I know the two you mention are very common across many applications.

You can read our documentation here.