Forum Discussion
Keyboard number pad #5 not recognized in Trigger
I'm having a problem with the Trigger Wizard and hoping someone can help. The trigger is simple. When the user presses "5" I want a feedback layer to show. The trigger is: "Show Layer BetterWay when the user presses 5 after clicking on this slide." The issue is, my users likely will be using a keyboard with a numeric keypad, and are more likely to reach for and use that than the numbers on their QWERTY keyboard. When I try to set up that trigger and use the numeric keypad's #5 key, the trigger literally does not respond to the key press. (If I press the numeric keypad for #1 or #2, however, it accepts it as "NumPad1" and "NumPad2", respectively. It works for all of the number pad keys except 4 and 5 (and unfortunately, I need 5 to work). I've checked that the "Num Lock" is on, and also tried it off. The key works when typing--just not for the Trigger. Any suggestions?
Has this been resolved?
Thanks for following up, Tiffany!
Looking over this discussion, I see a couple of different issues raised. Could I have you share your file here along with answers to the questions below so we can help determine what's happening?
- Are you experiencing an issue where the trigger "When the user presses" isn't defining the number 4 or 5 on the number pad?
OR
- Is the incorrect feedback layer appearing when you're using the correct keyboard shortcuts?
Hi Eric!
Thank you for bringing this up! I see that we've logged this as a software bug where the trigger "When the user presses" isn't defining the number 4 or 5 on the number pad. I've added your comments to our report to update this discussion when we have news to share.
I appreciate you taking the time to share this with us!
I'm seeing the same behaviour when pressing the + on the number pad. Is this also part of the bug or intended behaviour?
Hi Christina,
Thanks for reaching out and sharing what you are seeing in your project file.
I did a quick test using the + sign on the QWERTY keyboard and the number pad and both seem to be working for me:
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
Thanks for checking in Leslie. I've looked at the problem file again and actually the problem is that I have a shortcut key freeform interaction and in that, using Ctrl + Numpad PLUS isn't working. Storyline is recognising that I'm pressing a key but it brings up the "incorrect" feedback layer even though I'm hitting the right keys. Could you confirm what the expected behaviour in a shortcut key interaction is and then I'll upload an example if need be. thanks, again!
Hello Christina!
I'm happy to help! It sounds like the incorrect feedback layer appears when you're using the correct keyboard shortcuts. That isn't expected behavior, so it would be helpful to test your file. Would you mind uploading the file privately?
Case 02649376 submitted. Thanks, Lauren.
I am experience this issue:
- Are you experiencing an issue where the trigger "When the user presses" isn't defining the number 4 or 5 on the number pad?
Has the issue been resolved? Or is there a workaround?
Hello Katrine!
Thank you for taking the time to share that you're running into this issue too! I've reported this issue to our Engineering team to see what might be getting in the way, specifically with the 4 and 5 keys on the number pad.
I'll update you in this discussion when I have more information.
Hi everyone!
Great news! We just released another update for Articulate 360 and included a few important fixes you'll see in the release notes.
The item you'll be interested in is:Fixed: Key-press triggers stopped working if they were set to fire when the learner pressed the number 4 or 5 on their keyboard.
Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.What a bizarre glitch.
And the time taken to fix it.
