Forum Discussion
Problem with keyboard navigation
Hello!
I'm using buttons to show additional text in layers but I'm having trouble with some of the buttons when I try to open them using keyboard navigation. I've made a copy of my project (see attachment).
When I tab to the first button (xxx 1) and hit enter, the layer wont show.
When I tab to the second button (xxx 2) and hit enter, the layer pops right up.
I can't figure out what the difference is between the buttons and why this only happens when I'm using keyboard navigation?
Thanks!
/Sofie
- Hi Sofie!
Thanks for reaching out and attaching your file so I could investigate!
I took a peek at your file and saw exactly what you described where tabbing to Button 2 and clicking Enter doesn’t show layer 1.The trigger looks correct, and I’m not sure why it isn’t working, so I recommend we start from scratch! Here’s what I did:- Deleted the trigger for Button 2, then recreated it. Now, in preview, I can tab to Button 2, click Enter, and layer 1 shows!
I’ve attached my revised file, so check it out and let me know if you see the same results on your end! Ah of course!
I have this problem on some buttons throughout my original project, so I guess I copied that button to other slides then. But now I know what to do. Thank you so much Becca! :)
I'm having this same problem. I'm using a mac with an M1 chip and running parallels to use Storyline. It is SO SLOW to create a new trigger--at least 10-15 seconds for each trigger. Copying and pasting a trigger and editing that in the trigger panel works at a normal speed, so I do that for almost everything. I made the mistake of not testing with a keyboard till after completing a huge course only to discover that almost nothing works with a keyboard because the triggers were not "new." Going back to create new triggers for everything is going to take at least a day. Is there a fix for this coming? This is a huge problem not just for those using an M1 but anyone who wants to set up triggers more efficiently. This seems like a pretty significant bug.
Hi Kristen, I am also using Mac with Parallels to run Storyline. In regards to the slowness, have you tried adjusting its Virtual Machine Configuration? You can refer to the article here https://kb.parallels.com/en/112091
Mine was very slow too, I've increased my Processors and Memory for Parallels manually and it helped and made it a bit faster.
Hi Kristen,
I'm sorry you're running into this snag! I have opened a support case on your behalf. You may have seen the support email that was sent. Our support engineers will be in contact soon to help you through this issue.
Thanks for reaching out!
