I know there are a lot of comments on this, and I've been able to get this to work in Storyline2, but I can't get the same methods to work in Storyline 360.
Basically, on the previous slide, I have it setup so you click a button that advances to the next screen, and on the next screen I want the cursor to be active in a text entry box (in a different location than the button being clicked).
I've tried Converting to Freeform Text Entry, and I've also tried inserting a data entry text box.
In both instances, I placed the text entry box on another layer, and I add a trigger saying to show this layer when the timeline starts.
This used to work in Storyline2 and it would autofocus the text entry box. Am I doing something wrong, or forgetting a step?
Just for my own sanity at this point, I opened up Storyline 2 and was able to get this to work as I described on my first try.
Screen 1 - Hotbox advancing to next slide
Screen 2 - Trigger to show a layer with a data entry text box when the timeline starts. The cursor auto-focuses in the data entry text box as soon as the slide starts, without needing to click into the data entry box
Hey David - Glad you were able to find something that worked for you, as well as saved your sanity :) I appreciate you popping back in with an update and for sharing with the community.
It actually isn't working yet. I meant that I tried the same things in Storyline2 and it works properly. When I try to do the exact same method it doesn't work in Storyline 360.
In 360, you still have to click inside of the text box to get it to activate (have the cursor start blinking).
Hello again David - Thanks for the steps needed to re-create the behavior you are seeing. After checking this out, I think it's more of a difference in Flash vs HTML5 output.
Here is my SL2 published test file. If you are viewing the Flash output, it works as expected. The HTML5 output does not auto-focus, even in SL2 though. Keep in mind that the preview for SL2 is Flash-based, so it looks great there as well.
Here is my SL360 published test file (upgraded from SL2 file). I published the same as SL2 standard with Flash first and HTML5 fallback and the Flash version works as expected, but the HTML5 version does not auto-focus. The preview for SL360 is HTML5, so the difference shows there as well.
All that being said, it is something we have shared with our team and I will add this thread as well for both users impacted as well as for update when applicable.
Oh wow, didn't even think that there could be a difference between the behavior of the text boxes between html5 and flash outputs.
Thanks for investigating and sharing with your team! The main reason we're upgrading to 360 is due to the security issues with Flash, and overall 360 does a much better job exporting to html5. Hopefully you guys can find a fix/work around for this.
My goal isn't really about a text box though, I just need to get focus back to the slide so the triggers I have set with fire without someone having to click on the slide.
Hi there, Seth. How does the learner get to the slide where you need the triggers to fire? If they are using player buttons, like Next, the focus stays on the player and not the slide. We're looking into that behavior.
Feel free to share a couple of example slides with what you need to do! This community is always happy to dig in.
I do not have an update to share on the question Seth raised above.
Phil has chimed in to share an idea with you.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
Hi everyone! I've been following closely this discussion 'cause I've faced the same issue more than once. I've tried the methods you describe down here: sometimes succesfully others not so much. Nevertheless, it's gratificating for me to inform that I've found the solution on the tool "Record Screen" (SL360). Once the program generates text natively I just duplicate it on the slides I need it. I share a video with the process.
I am having the same issue. I moved the text entry to the bottom of timeline and the cursor was active. So that worked. However, I am using text entry in a software sim and the text entry cannot be at the bottom of the timeline. It has to be on top of the screenshots.
Thank you for letting us know! Just to make sure I am on the same page, the Text Entry box works at the bottom of the timeline but isn't working when moved to the top?
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it privately to our Support Engineers. Either way, we will delete it when finished troubleshooting.
Hi, sorry for the long delay... I "fixed" this by essentially telling the user they had to press the tab key to "activate" the arrows I wanted them to be able to use (the arrows are the only items in the tab order on the slide, and thus what *should* have been in focus if the focus left the slide controls. This is all centered around accessibility. I have a list of items that a leaner will step through, and they can use on-screen buttons (arrows) on the screen to do so. To make it compliant I make sure a learner can use the keyboard only, but it was getting "Stuck" when someone advanced to the slide which contained the arrows because the directions indicate you can use the arrow KEYS on the keyboard as well (there are triggers for the buttons to enable this) but without it being focused on the screen content, those triggers would not do anything. Ergo, adding the (somewhat cluggy) instruction to "press the tab key to activate the arrow keys" does the job... for not at least.
Thank you for reaching out and sharing those details! I am glad to hear that you were able to find a workaround and I will pass this along to our team.
We will be sure to update this thread with any relevant information as well!
Thanks Seth! We decided to instruct our learners to first click in the box then enter their response. I've been to websites where I can just start typing...and some sites where I start typing and nothing happens and then I just know to click in the text entry box. That extra click really bothers some folks. Depending on the audience, it can be a show stopper.
Vincent, do you still want to see a sample file where this is occuring?
If you don't mind sharing an affected .story file, we'd love to take a closer look at that behavior to explore further! You can send it privately to us by using this link. We'll delete it after troubleshooting.
23 Replies
Just for my own sanity at this point, I opened up Storyline 2 and was able to get this to work as I described on my first try.
Screen 1 - Hotbox advancing to next slide
Screen 2 - Trigger to show a layer with a data entry text box when the timeline starts. The cursor auto-focuses in the data entry text box as soon as the slide starts, without needing to click into the data entry box
Hey David - Glad you were able to find something that worked for you, as well as saved your sanity :) I appreciate you popping back in with an update and for sharing with the community.
It actually isn't working yet. I meant that I tried the same things in Storyline2 and it works properly. When I try to do the exact same method it doesn't work in Storyline 360.
In 360, you still have to click inside of the text box to get it to activate (have the cursor start blinking).
I apologize, I misread your post. I'll take a look at the steps to replicate you shared above.
Hello again David - Thanks for the steps needed to re-create the behavior you are seeing. After checking this out, I think it's more of a difference in Flash vs HTML5 output.
Here is my SL2 published test file. If you are viewing the Flash output, it works as expected. The HTML5 output does not auto-focus, even in SL2 though. Keep in mind that the preview for SL2 is Flash-based, so it looks great there as well.
Here is my SL360 published test file (upgraded from SL2 file). I published the same as SL2 standard with Flash first and HTML5 fallback and the Flash version works as expected, but the HTML5 version does not auto-focus. The preview for SL360 is HTML5, so the difference shows there as well.
All that being said, it is something we have shared with our team and I will add this thread as well for both users impacted as well as for update when applicable.
Oh wow, didn't even think that there could be a difference between the behavior of the text boxes between html5 and flash outputs.
Thanks for investigating and sharing with your team! The main reason we're upgrading to 360 is due to the security issues with Flash, and overall 360 does a much better job exporting to html5. Hopefully you guys can find a fix/work around for this.
Hey folks! I'm happy to let you know that we just released Update 12 for Storyline 360, and you can check out the new features and fixes here!
Specifically included in this version is a fix to address some issues with data entry fields:
Simply update Storyline to the latest version and republish your project to see the fix. Here's how updating Storyline 360 works.
I'm happy to hear how you make out!
I just had a chance to make a course utilizing this method.
I wanted to write back and confirm that after downloading the updated version, the text box does in fact auto focus again!
The trick of putting the text box on a new layer and then a trigger to show the layer once the time line start works.
Thank you!!!
Thanks for popping in to share David :) Happy to hear that it's working well for you.
This does not seem to work anymore?
My goal isn't really about a text box though, I just need to get focus back to the slide so the triggers I have set with fire without someone having to click on the slide.
Any ideas on either would be great!
Hi there, Seth. How does the learner get to the slide where you need the triggers to fire? If they are using player buttons, like Next, the focus stays on the player and not the slide. We're looking into that behavior.
Feel free to share a couple of example slides with what you need to do! This community is always happy to dig in.
This post was removed by the author
adding the text entry field to the very bottom of the timeline should do this
Hi Richard,
I do not have an update to share on the question Seth raised above.
Phil has chimed in to share an idea with you.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
This post was removed by the author
I think this is because the question is a numeric entry, seems like text entry will grab focus but numeric entry will not.
This post was removed by the author
Adding a text entry to that slide and dropping to the bottom of the timeline and it works.
Also creating a freeform text entry the focus works as well
Hi everyone!
I've been following closely this discussion 'cause I've faced the same issue more than once. I've tried the methods you describe down here: sometimes succesfully others not so much. Nevertheless, it's gratificating for me to inform that I've found the solution on the tool "Record Screen" (SL360). Once the program generates text natively I just duplicate it on the slides I need it. I share a video with the process.
Video-click here
I am having the same issue. I moved the text entry to the bottom of timeline and the cursor was active. So that worked. However, I am using text entry in a software sim and the text entry cannot be at the bottom of the timeline. It has to be on top of the screenshots.
Hey Doug,
Thank you for letting us know! Just to make sure I am on the same page, the Text Entry box works at the bottom of the timeline but isn't working when moved to the top?
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it privately to our Support Engineers. Either way, we will delete it when finished troubleshooting.
Hi, sorry for the long delay... I "fixed" this by essentially telling the user they had to press the tab key to "activate" the arrows I wanted them to be able to use (the arrows are the only items in the tab order on the slide, and thus what *should* have been in focus if the focus left the slide controls. This is all centered around accessibility. I have a list of items that a leaner will step through, and they can use on-screen buttons (arrows) on the screen to do so. To make it compliant I make sure a learner can use the keyboard only, but it was getting "Stuck" when someone advanced to the slide which contained the arrows because the directions indicate you can use the arrow KEYS on the keyboard as well (there are triggers for the buttons to enable this) but without it being focused on the screen content, those triggers would not do anything. Ergo, adding the (somewhat cluggy) instruction to "press the tab key to activate the arrow keys" does the job... for not at least.
Hey Seth,
Thank you for reaching out and sharing those details! I am glad to hear that you were able to find a workaround and I will pass this along to our team.
We will be sure to update this thread with any relevant information as well!
Thanks Seth! We decided to instruct our learners to first click in the box then enter their response. I've been to websites where I can just start typing...and some sites where I start typing and nothing happens and then I just know to click in the text entry box. That extra click really bothers some folks. Depending on the audience, it can be a show stopper.
Vincent, do you still want to see a sample file where this is occuring?
Hi there, Doug!
If you don't mind sharing an affected .story file, we'd love to take a closer look at that behavior to explore further! You can send it privately to us by using this link. We'll delete it after troubleshooting.
This discussion is closed. You can start a new discussion or contact Articulate Support.