I'm using Storyline 2 and built a trigger that to change the state of an image when the user hits Ctrl + C on the keyboard. It's not working and I can't figure out why for the life of me. Any help?
If you view an Articulate Storyline course on your local hard drive (or send it to someone else to view on their local hard drive), you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features to fail. To properly test your published content and share it with others, upload it to the environment for which it was published. See this article for details.
It may be that those keystrokes you've set up are actually triggering something within the web browser which is the parent application and will receive the keystrokes as described here.
But the issue isn't in the browser, that is where CTRL + C is working and the state changes.
It is when you preview the slide in Storyline that the CTRL + C isn't working which I have to assume is because that key combo is reserved for copying in storyline, but I would have thought it would have worked in the preview.
For example in her storyline file I changed the trigger to CTRL + I and the state changes when I preview in storyline and press that key combination.
When I switch it back to CTRL + C the state won't change in the preview when those keys are pressed.
Thanks everyone. I learned (1) I did indeed set up the trigger correctly, (2) that particular key combination is used as a feature in Storyline 2 and thus will only function as a part of the module when it has been published.
8 Replies
I took a look at it and noticed that it doesn't work when you preview the slide.
I found that if you publish the project it works.
Not sure if this is a design of storyline or a bug.
Hi Kesha and Gary!
If you view an Articulate Storyline course on your local hard drive (or send it to someone else to view on their local hard drive), you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features to fail. To properly test your published content and share it with others, upload it to the environment for which it was published. See this article for details.
I don't think that is the issue here Leslie.
When you preview the slide in Storyline it doesn't recognize CTRL + C being pressed, but when published it does.
I published it to my hard drive and it recognized the keys being pressed and changed the state in the browser locally.
This post was removed by the author
It may be that those keystrokes you've set up are actually triggering something within the web browser which is the parent application and will receive the keystrokes as described here.
But the issue isn't in the browser, that is where CTRL + C is working and the state changes.
It is when you preview the slide in Storyline that the CTRL + C isn't working which I have to assume is because that key combo is reserved for copying in storyline, but I would have thought it would have worked in the preview.
For example in her storyline file I changed the trigger to CTRL + I and the state changes when I preview in storyline and press that key combination.
When I switch it back to CTRL + C the state won't change in the preview when those keys are pressed.
Yes, Gary. As I shared above, some things differ in preview vs publish and we are aware of a few triggers that do not work in preview.
Thanks everyone. I learned (1) I did indeed set up the trigger correctly, (2) that particular key combination is used as a feature in Storyline 2 and thus will only function as a part of the module when it has been published.
Thanks for the update Kesha :)
This discussion is closed. You can start a new discussion or contact Articulate Support.