Conversion of SL2 to SL3 and Next/Previous Hot Key Buttons

We are in the process of converting our SL2 projects into SL3.  All SL2 Projects had a hot key for the next slide (N) and the previous slide (P) which were located in the Slide Triggers.  We noticed that when we converted, all the N and P slide triggers moved down to the player Triggers.  You can double click in the player triggers to move them back to the slide trigger but as soon as you close out of the project file, they will revert back to the player trigger (see attachments). When you publish out in SL3 hot keys work great if the N and P were in the Slide Triggers originally. However, when you reopen the project and publish out again (keep in mind the P and N have now automatically moved to the player trigger) the hot keys work but if you answer a question slide and press submit you will move to the next slide.  The problem is, if you press previous and then try to use your mouse to move to the next slide.  The next button is deactivated with the mouse.  Has anyone else experienced this or know of a workaround?

27 Replies
Alyssa Gomez

Hey Erin! You have a great question, and I'm happy to help here.

I did notice that the key press trigger to jump to next slide in Storyline 2 is listed under Slide Triggers and in Storyline 3 is listed under Player Triggers.

Normally that wouldn't cause a problem, except that there's a bug lurking in Storyline 3 with key press triggers.

In Storyline 3, you have to click the slide before the key press trigger will work. We've been working on this issue, and fortunately it's going to be fixed in the next update of Storyline 3.

This video explains everything. Have a look, and let me know if you have any questions! 

Crystal Horn

Hey Erin. 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!

Erin V

Leslie/Crystal,

Still having the same issue. We have figured out a work around for now but we were hoping the issue would be resolved.  I'm attaching a file.  When you get to the question slide. Make a selection and then press continue.  On the next slide press the previous button and then try to click the next button with your mouse (the N hot keys works).  The next button with your mouse is disabled because the N is in the Player Trigger instead of the Slide trigger. If you try to move the N and P to the slide trigger, SL3 will push back down the player trigger every time. Let me know if you have any questions.  Thanks

Alyssa Gomez

Hi Erin!

I'm definitely seeing where the "Next" button is non-responsive when you click on it with the mouse, but I would also think that is happening because the Next button doesn't have a trigger in the trigger panel. 

You mentioned that these slides worked correctly in Storyline 2. Do you have the Storyline 2 backup file? I'd like to test the same interaction in Storyline 2. Thanks!

Ashley Terwilliger

Hi Erin,

Thanks for sharing your Storyline 2 file. I took a look and saw the same thing that you mentioned upon upgrading it to Storyline 3. I also looked at adding in a new slide to your Storyline 2 course, upgrading it and adding a new slide to your Storyline 3 and creating a brand new Storyline 2 course which was upgraded. All of these were with a quiz and those worked normally (upgrading or the new slide insertion into Storyline 3).

Since your slides had a lot of extra layers and additional components, I'm not sure if that's causing the issue with the next button not working on the revisit to your question slides. Can you tell me if you've seen the same issue appear on a basic quiz slide (feedback laters, no next button enabled until revisit/review, etc.)?

The slide triggers and player triggers do change location in the trigger panel, and that's something we have reported to our team.

 

I attached the basic SL2 and SL3 files I was working with in case you'd like to take a look at those and let me know how it behaves on your end. 

Erin V

Ashley, I took the SlidenextSL3.story file you loaded and duplicated the test question. I added an N hotkey on slide 1.2 (see attachment) and I am having the same issue. Once I answer the question and if I press previous, the next button is disabled using the mouse or tabbing to the next key. The only way to advance is to use the N key (as long as you are in the project, not in the skin.  Apparently this isn't just a problem with our design.

Any suggestions?

Thanks,

Erin

Alyssa Gomez

Thanks so much for sharing that updated file, Erin. I'm seeing the bug clearly now.

The keypress triggers were listed as Slide Triggers in Storyline 2. After upgrading to Storyline 3, those triggers were placed under Player Triggers, and this caused them to work incorrectly. 

I'm going to share this bug with my team so we can begin looking at next steps. In the meantime, there is something you can do to work around this bug--check out this video for a demo of the workaround steps.

Erin V

Hi Alyssa,

I appreciate the quick response.  However, your fix won't work. I've already tried it.  You can move the N and P to the Slide Triggers while the project is open. Once you close out and reopen the file they will automatically jump down to the Play Trigger. :(

We did come up with a temporary solution until the issue is fixed.  On our questions slides, we added the N and P hot key to the Slide Master and that seems to be working.  Finger crossed. 

Katie Riggio

Hi there, Hy. Happy to help! 

We're no longer experiencing the issue shared here where slide triggers would move to the Player trigger in Storyline 360. Can you tell me a little more about your file?

  • What Storyline 360 update are you using? You can find this detail by clicking on the Help tab, then About Storyline.
  • Was your project upgraded from an older version of Storyline?
  • Would you mind sharing a troublesome slide or two with us? It'll help us get a clear picture of what's happening, and we'll delete it after troubleshooting. You can send that Storyline file to us privately in a case here