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

Alyssa,

Thank you for the reply.  Any idea when this will be corrected in SL3?

Thanks,

Erin

Hey Erin,

This has been corrected in Storyline 360 and will be included in the next update of Storyline 3. I don't have a date to share, but we have this thread attached, so that we can update you here.

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!

Thank you for the update.  I don't think I read where the Next and Previous slide triggers moved down to the player Triggers.  Did I miss that? 

Hey Erin,

Check out this documentation to understand trigger locations.

Thank you for the information Leslie, but the issue listed above remains.  I tested it out again this morning and I am running into the same issue.  :(

Hi Erin,

I apologize. I didn't realize you were still battling this. 

Did you update your Storyline 3 software as Crystal shared above?

Would you be able to share a .story file and the steps to replicate so that we can take a closer look?

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

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!

Alyssa,

We've never had a problem with this functionality until Storyline 3. I am attaching a similar project that was created in SL2 and works properly.  Let me know if you have any questions.  Thanks.

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. 

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

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.

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. 

Hi Alyssa

I can confirm Erin's response - it happens the same in SL360. Once you close and re-open the file the triggers reset.

Oh no! Thanks so much for catching that, Erin and Wendy. I'll add that to our bug report. As soon as a fix is in place, I'll let you know!

Hi Alyssa

here is the case # 01287155 I had logged with Ryan from 3/3

Thanks, Wendy for the case number - and I see that Ryan connected it to the bug report we had, so I've looped in this discussion too. 

Hello,

Just following up to see if we are any closer to a resolution to this issue?

Thank you

Thanks for checking in, Erin, and I'm really sorry for the headaches this bug is causing you. Our team is still investigating this issue, and we'll be sure to let you know as soon as a fix is released. 

Good morning,

Any update on this issue?

Hi Erin,

Our team is still monitoring this bug. I have this thread tagged to be updated as soon as we have any forward movement towards a fix. Thanks for checking in!

No movement forward on this bug still @Alyssa Gomez?

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.