I'm adding key press triggers for accessibility. I need to use Alt+Right (to go to Next slide) or Ctrl+Left (to go to Prior slide). This works fine until I get to a branching scenario. I want the Alt+Right/Next to go to Slide 6.13, not to Slide 6.2 (which is numerically next). I've added/deleted/re-added this Key Press trigger and it's only going to Slide 6.2. See attached for triggers. Thanks in advance for any insight!
It's really odd that that the key press won't respond correctly in your project.
I've found that sometimes attaching a trigger to something on the stage rather than just the slide makes them work more reliably. I've added an invisible button (It's transparent), made it the same size as the slide, and put it in the background. Now the trigger is attached to the button instead of the slide, and it responds as it should.
I know this is a work around, but it should get your project working for you.
Yes, it looked correct. I think it has something to do with the way the trigger is attached to the slide container instead of an object on the stage. Sometimes the hierarchy in HTML5 is a little finicky, and the Engineers are still working out some of the fine details. But attaching the trigger to a background element solves that issue.
6 Replies
Hi Karen,
I tried to simulate what you are doing, and it works fine for me. Can you post your project so someone can look at it for you?
Dave
Dave, I pulled out just the scenario scene. I'd appreciate any info on where I've gone wrong.
Thanks!
Hi Karen,
It's really odd that that the key press won't respond correctly in your project.
I've found that sometimes attaching a trigger to something on the stage rather than just the slide makes them work more reliably. I've added an invisible button (It's transparent), made it the same size as the slide, and put it in the background. Now the trigger is attached to the button instead of the slide, and it responds as it should.
I know this is a work around, but it should get your project working for you.
Dave
Otherwise it all looks correct to you? Curious!
Thank you for the help! I really appreciate it!
Yes, it looked correct. I think it has something to do with the way the trigger is attached to the slide container instead of an object on the stage. Sometimes the hierarchy in HTML5 is a little finicky, and the Engineers are still working out some of the fine details. But attaching the trigger to a background element solves that issue.
Dave
Thank you again for your help. I'll try to get it all working now!
This discussion is closed. You can start a new discussion or contact Articulate Support.