SL360 key press trigger issues

Hi, I am just trying converting an SL2 course to 360 and testing for accessibility and tab functionality. With SL2 with certain interactions I would often have a layer labelled accessibility which would be triggered by (user presses a key) pressing of the tab key. This no longer works and the layer no longer opens when tabbing from a previous page. However when I exit the course and then resume, the tab button opens the accessibility layer and tabs through as normal. Out of interest I have tried a different key entry trigger and this doesn't work either. 

I have sent a support case but was just wondering if anyone else has experienced this.

42 Replies
Alyssa Gomez

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. 

Andrew Clarke

I am having a similar issue with SL360 (not tried in SL2).

Each slide has a hidden 'presenter notes' layer that is shown when the 'p' key is pressed.

If the first interaction is a key press - this trigger does not work.

If another interaction takes places first within the module (e.g. a mouse click on another slide) the key press triggers do work.

Please do update is you have a solution.

Thanks,

Andrew

 

Alyssa Gomez

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. 

Heather Morgan

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

Karen Johnson

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?

Learning Agency  Team

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?

Crystal Horn

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!

Dee Cee

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

Alyssa Gomez

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?
Dee Cee

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

Jeremy Larson

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!

 

Leslie McKerchie

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.

Crystal Horn

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!