Forum Discussion
Storyline press key trigger: Can I remove the click requirement?
In previous versions of Storyline, the press key trigger did not require a previous click. Now it only works when the user presses a key after clicking an object.
Can this requirement be removed? It would be helpful if it was optional or the action could be a choice rather than clicking. The issue I'm trying to resolve is in screen recording simulations with Text Entry objects. The user can press Enter to move to the next slide. They might not have clicked anything before the place where I want to add the trigger.
The screenshot shows how the trigger looks.
- RonPricePartner
You can add conditions in the conditions section of the trigger
- S-JBirchCommunity Member
Would you consider changing the trigger wording to "after timeline starts on this slide"?
The wording "clicking on this slide" is not clear to me, as it seems you don't have to click anything before pressing the key of the trigger.
- MarianneSeid410Community Member
Thanks, Ron! It would be nice if you could change the condition, though. You might want it to work after a variable change or a state change, or some other action.
- MauraSullivan-9Community Member
+1 for making the requirement of "clicking on this slide" optional and allowing it to sometimes be based on the timeline.
- RonPricePartner
Hello Marianne,
If you leave the default "after clicking on this slide" you should be golden.
- MarianneSeid410Community Member
Thanks!
- NeilBlan-c75c04Community Member
The requirement of clicking somewhere on the slide isn't a helpful or versatile change, why was this implemented? Is it possible to revert? Thanks!
- S-JBirchCommunity Member
I'm afraid we have reached the stage where Articulate can be bothered with improving the base features of Storyline or fixing mistakes made. It feels like It's all AI from here on! There are hundreds of deficiencies and annoyances in the software that should be fixed. They've been here for years.
- NeilBlan-c75c04Community Member
I just can't figure out why that change was made in the first place. I had used it to create easy navigation for visually impaired people and now it's back to the drawing board.