Hello, I upgraded to the new version on 11/20/19 and ever since have had issues with a trigger not working properly. I have one trigger that is supposed to show a layer when you press the F2 key after clicking on a text entry field on the Base Layer. The trigger seems to "fire" because I briefly see the layer but then it is as if the layer is immediately hiding. There is no trigger to hide the layer at all.
Alia, I think I am having a similar issue, I posted a discussion about the "new" way the keypress trigger is set up... could this be the same issue for you?
Hello! I'm wondering about this? I'm trying to implement accessibility, which requires keyboard only navigation, and thanks to the latest update, the key press trigger requires that the user click on something. This seems like backwards functionality and breaks my accessible lesson. Have either of you found a workaround? It's even recommended to add this trigger in the Articulate blog article from a while ago - and now that doesn't work... https://articulate.com/support/article/Storyline-360-How-to-Design-an-Accessible-Course
I'm happy to test this out on my end to see if we can offer a workaround. Would you mind sharing your file? You can share it by using the "Add Attachment" button in this discussion.
I have had various issues with triggers for layers since my last update to Storyline 360. Sometimes they seem to only be glitchy once published but now I see it when building. I have attached one slide where I have created cue points that should trigger the layers to show at those points. But nothing shows. I have it stripped down to just a handful of assets, a video clip, some audio, and the layers. Not sure if this is similar to others issue, but this was the closest thread I could find to my problem. Hope there is a solution.
I appreciate you taking the time to add the .story file! After digging into the file, I can see that the objects on each layer are not at or near the beginning of the timeline. The timeline on the layers isn't long enough to display objects at 7sec.
7 Replies
Hi Alia
if you can share the slide it will be easier for someone to try and help you.
Alia, I think I am having a similar issue, I posted a discussion about the "new" way the keypress trigger is set up... could this be the same issue for you?
https://community.articulate.com/discussions/articulate-storyline/key-press-trigger-hoping-i-m-missing-something
Hello! I'm wondering about this? I'm trying to implement accessibility, which requires keyboard only navigation, and thanks to the latest update, the key press trigger requires that the user click on something. This seems like backwards functionality and breaks my accessible lesson. Have either of you found a workaround? It's even recommended to add this trigger in the Articulate blog article from a while ago - and now that doesn't work... https://articulate.com/support/article/Storyline-360-How-to-Design-an-Accessible-Course
Hello Susi!
I'm happy to test this out on my end to see if we can offer a workaround. Would you mind sharing your file? You can share it by using the "Add Attachment" button in this discussion.
Hi!
I have had various issues with triggers for layers since my last update to Storyline 360. Sometimes they seem to only be glitchy once published but now I see it when building. I have attached one slide where I have created cue points that should trigger the layers to show at those points. But nothing shows. I have it stripped down to just a handful of assets, a video clip, some audio, and the layers. Not sure if this is similar to others issue, but this was the closest thread I could find to my problem. Hope there is a solution.
Hi Pamela!
I appreciate you taking the time to add the .story file! After digging into the file, I can see that the objects on each layer are not at or near the beginning of the timeline. The timeline on the layers isn't long enough to display objects at 7sec.
I've walked you through my testing in this short tutorial!
Thank you, Lauren. Having the video was extremely helpful!
This discussion is closed. You can start a new discussion or contact Articulate Support.