Forum Discussion
What's the best way to create a custom keyboard shortcut for a button?
One of my chief complaints about feedback buttons in pop-up windows (like feedback layers) is the disconnect between the baked-in player controls when it comes to keyboard shortcuts. I can press Ctrl + Alt + . to go to the next slide, Ctrl + Alt + , to go to the previous slide, or Ctrl + Alt + s to submit, but if it's a question slide with feedback, then I'm pretty much guaranteed that the feedback layer will have a big Continue button with no shortcut key assigned to it.
I considered just adding a key press trigger to the button or layer itself, but that seems awkward: it says, "when the user presses the key after clicking on the object/layer." So then, the user is going to have to click the layer before they can press the shortcut key? That seems like more of a roadblock than just no shortcut key at all.
I also considered changing the standard behavior of the feedback layer to allow access to the base layer's built-in navigation buttons, But the issue there is that a question slide displays a Submit button instead of a Next button, even after the answer has been submitted.
Am I missing something? Is there an easier way to accomplish this?
1 Reply
Hi Greg,
Might I suggest implementing and then ignoring the trigger's condition of "after clicking on this layer"?
It appears to me that Storyline requires this condition in the programming of the trigger but does not actually enforce it as we might think.
I tested putting a trigger on a quiz slide's feedback layers (both correct and incorrect) that stated "Jump to next slide when the user presses a key (the #1 key) after clicking on this layer." However, when testing it, I chose my answer on the quiz slide, the appropriate feedback layer appeared, I pressed the #1 key, and I was instantly taken to the next slide. Note that I did this without a separate additional click of the mouse on the feedback layer.
My theory is that Storyline considers accessing the feedback layer the same as clicking on it. In other words, once the feedback layer is activated and displayed, Storyline may consider that you have "clicked on it," thus making the keyboard shortcut you have programmed in the trigger accessible.
So, I would suggest adding in the triggers on the feedback layers to enable your programmed keyboard shortcuts, include the trigger condition of "after clicking on this layer," and then ignoring the condition in actual practice. It seemed to work for me.
Here is my test Storyline file:
