SL360 key press trigger issues

Just wanted to pop in an share an update that Eloisa was able to reproduce the issue, and it has been submitted it to our Quality Assurance team for further review. Unfortunately, she was unable to find a workaround, other than pressing the Tab key first on the slide. At this point, we can't offer a time frame for when or if this issue will be fixed, but I'll be sure to come back and share additional updates if Quality Assurance finds a different workaround for it in the meantime. 

Hello Andrew!

Thank you for sharing your experience with us. We have shared this information with our QA team, and we’ll be sure to post any updates here in this discussion!  You’ll receive an email notification because you are now subscribed to this post. A workaround I would suggest for now is to press Tab then P to view the 'presenter notes' layer. 

I am having this same issue. In my case, it is a shape that is initially set to a hidden state with a trigger to change the state to normal if the user presses the "H" key. It is meant to show a "hint" of where the user should click to advance to the next slide. It worked perfectly in SL2, but after upgrading to SL360, the user has to click somewhere on the screen before the "H" key will work. This is very frustrating! I was wondering if there has been any resolution to this issue.

Thanks,

Heather

Same issue here, too - attempting to use the "insert" text field - have the learner type in the required item, and then use the "press tab" trigger to move to the next layer. Instead of tabbing to the next layer, it actually tabs to different areas on the 360 current screen.  The systems that the learner is using requires the tab key to be pressed to go to the next field - any work around possibly?

Hello Karen!

Sorry to hear that you ran into difficulty with this, but I've seen this discussed in the forums.

The Tab key is used for accessibility, so it sounds like that is what you are experiencing.

Tab Order may be able to assist you as this community member shared here.

Hi, im having the same issue. In my course, users progress using a key press. This doesn't work if they don't press the window first with the mouse. This is a huge problem for us, since we have a big course and the client requested the key pressed feature. 

Is there any update on when this will be fixed?

Hey Rasmus!

I can see this is causing you some headaches, I'm sorry about that! My colleague Alyssa and I just replied to you over in this thread and I wanted to pop in here to link the two for ease of access. 

Welcome to E-Learning Heroes by the way! Happy you're here ☺️

Hi everyone!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.

We fixed some triggers that didn't always work correctly in HTML5 output, including triggers that execute when clicking outside an object, key-press triggers, and conditions that compare two numbers.

Just launch the Articulate 360 desktop app on your computer and click the Update button for each application.

Let me know if you have any questions, or feel free to reach out to our support team!

Hi Crystal,

Will this fix be made in Storyline 3 and if so, do you have an delivery date estimate?

Hi Douglas,

Yes, we'll include this fix and other recent ones in the next update of Storyline 3. We don't have a date set for that yet, but once we have a bit more information to share we'll let you know here. 

Thanks for checking in! 

Hi all,

I just updated SL360 and now my key press triggers have all stopped working. This project is turning into an absolute nightmare. It seems that every time one bug that is hindering my course development gets fixed, another one pops up. In the last couple of weeks an issue with zoom was fixed which seemingly created a problem that caused my screen to flash when slides transitioned. Now that this is fixed, all of my key press triggers have broken and I am not sure what to do to fix them. As my screen is a simulation, it relies heavily on key presses to move the course forward. Now that they are all broken, my course is unusable. Please can you do something to fix this? 

Thanks,

Derek

Hi Derek,

I'm really sorry that happened, and I want to make sure we get this fixed. 

I'd like to recreate a sample file for my team that displays this problem. Can you tell me more about the key press trigger you're using? 

• Are you using a text entry slide with a keypress to submit the answer?
• Can you share a screenshot of the slide and trigger?

Hi Alyssa,

I am using a text entry slide with a keypress to trigger the next slide. So
for example, the user types 'Dub' and the trigger is set to move to the
next slide when they click 'b'. The weird thing is that when I created a
new storyline course and made a similar trigger on that, it worked. It just
appears to have broken the ones on my existing course. I tried copying my
existing slides over to a new project but that doesn't work and deleting
the existing text entry box and replacing it with another doesn't fix it
either.
I can't post a screenshot publically but I have opened a bug report (
01188846) and uploaded my course there.

Thanks,
Derek

Thanks Derek for reaching out to our team and sharing the file privately.

Thanks for those details, Eric. I also couldn't recreate the problem in a new file, so thank you for sending your file over to our team. We'll take a look and be in touch soon!

Any resolution found to this? I just captured my firs simulation in a month (using SL360) and none of the text triggers seem to be working. Please help as this is a critical function for how our company uses Storyline.

Hey Derek, have you gotten any resolution to this. I am capturing my first simulation in the last month and I am experiencing the same problems. None of my text interactions/triggers are working on old files and it does not seem to work in any of my new screen captures as well. I'd love to hear any solutions or workarounds that you or Articulate may have found. Thanks!

Opened a case regarding this issue. I hope to hear from you guys soon. 

Thanks for reaching out Jeremy and letting us know that you filed a support case with our team. We do have an open issue based on Derek's case submission, and you should be hearing from someone soon.

Hello everyone,

Great news!  We just released another update for Articulate 360, and included a few important fixes that you'll see in the release notes here.  

The item you'll be interested in is:

We fixed several issues with triggers in HTML5 output, including on-click triggers that would automatically execute when using keyboard navigation to tab between objects, key-press triggers that wouldn't jump to the next slide when they were assigned to data-entry fields, and inconsistent hover triggers.

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.

Hi Jeremy. Apologies for only replying now. Hopefully, the update has fixed your problem but if not, I found that if I did not change the dimensions of the text entry field from their default size, the key triggers worked. 

Hey everybody. I'm excited to let you know that we just released update 3 for Storyline 3! It includes new features and fixes - check them all out here.

One of the fixes addresses an issue where the trigger "when user presses a key" was not functioning unless you pressed the Tab key first.

Here’s where you can download and install the latest version of Storyline 3. Let me know how you make out!

Hello, I'm running into this same issue.  I have the latest version of 360 installed.  I'm using a simple key press to advance a slide but the user still needs to click the slide in order for the key press to work. Any progress?

Hi there Susan! Thanks for reaching out to us!

The most common reason why a keypress trigger wouldn't work would be the Object of the trigger. The Object should be the slide itself, not an object on the slide.

Here's a quick video demonstration to show you what I mean. Let me know if that solves it!