I've got a series of simulations which include multiple text entry fields/interactions.
Is there anyway of ensuring that when the slide first loads that the focus is on the text entry field automatically i.e. the text can be entered without the user having to complete the additional step of clicking into the field (which has already been done as the preceding action) - there is the option to 'merge' the steps but this would create quite a lot of additional work across 3 playback modes so am hopeful there is an alternative approach...
Thanks Leslie - all I want is for the cursor to appear in the text entry field automatically - I've tried moving the text entry field to the last spot on the timeline as suggested in other posts on this forum but to no avail.
Are you utilizing the latest update to your software?
You may find that a data-entry field doesn't have focus when you visit a slide in your published output. As a result, you have to click the data-entry field before you can begin typing in it.
This issue was corrected in Update 5 for Articulate Storyline 2.
I worked this one out through trial and error eventually and have yes now updated to most up to date version. When I clicked on Check for Updates from within Storyline it wasn't brought to my attention that a new update was available - how does one keep oneself appraised of these updates? Thanks,
Just for anyone looking a solution to this potentially frustrating issue...there are a few things I did to make sure that when any of my pages with text entry fields loaded, the cursor in the text entry field was in focus.
1. Make sure that the text entry item on your timeline (e.g. Text Entry 1) is the first thing at the bottom of your timeline.
2. If you have any background images on your timeline (e.g. screenshot of the software you are developing training for), put that image on a masterslide layout, delete the actual image from the slide itself, and use the masterslide layout with the image on it instead.
3. Finally, Alt text. Make sure no other items on the screen are "visibile to accessibility tools". Only the text entry field should be visible to accessibility tools (including any objects on the master slide).
In my experience, these 3 things have solved this issue for me. Hopefully it works for you and saves you a lot of time and frustration!
Many thanks for stopping in to share your discoveries, Sanjay! Hopefully that will assist many others in the future who come across this post seeking assistance. :)
1607:1221 doesn't seem to fix it for me. If the text entry field is the only field into which a user can enter data, then it should automatically gain the focus. How hard is that?
Not sure if you responded via e-mail, but there is no attachment to your post. Please pop into the forums and utilize the 'Add Attachment' option in the bottom left of the reply window.
Thanks for the details and for sharing Perry. Looks like our QA Team is looking into some similar reports. I will add this thread for their awareness and so that we can update here when applicable.
So it means that this bug wasn't fixed in a previous update after all right?
In a step-by-step test with screen recording when splitting into slides it didn't split the one with text input. I copied the previous slide, adjusted the timeline and added a data entry field but it just doesn't focus when I preview.
Already changed tab order and timeline. The field cannot be the first at the bottom or it will be below the recording.
Any idea when this will be fixed?
Most of the times when I copy a field that is in focus from another project it works.
Your reply before mine was posted 15 days ago saying the QA team is looking into this.
My issue is the same as the OP but the text entry field is on a screen recording and not screen shot. I further explain the situation in my previous post.
The issue is the same that is said to be solved in update 5. It is not, or not completely at least.
Please re-read OP and my previous comment and let me know if you still have questions.
I have tried these fixes in Storyline 2 and in 360 and I cannot get the text entry box to autofocus. This is very urgent for a simulation we are creating. Please can you help. I have also tried adding javascript to autofocus it but nothing has worked yet.
Hi Stephanie - I do not have an update to provide on this issue as it is still in the hands of our QA Team, but I have updated to reflect that another user has been affected and perhaps we can get this prioritized in our internal conversations.
26 Replies
Hi Greg! I would advise following the editing tips in this tutorial. You can delete unnecessary slides as well as remove parts of a slide if needed.
Thanks Leslie - all I want is for the cursor to appear in the text entry field automatically - I've tried moving the text entry field to the last spot on the timeline as suggested in other posts on this forum but to no avail.
Thanks Greg!
Are you utilizing the latest update to your software?
You may find that a data-entry field doesn't have focus when you visit a slide in your published output. As a result, you have to click the data-entry field before you can begin typing in it.
This issue was corrected in Update 5 for Articulate Storyline 2.
I worked this one out through trial and error eventually and have yes now updated to most up to date version. When I clicked on Check for Updates from within Storyline it wasn't brought to my attention that a new update was available - how does one keep oneself appraised of these updates? Thanks,
Greg
Hi Greg! You can set up to auto-check for updates in your options as explained here.
The same link I shared above stays up to date as well :)
Just for anyone looking a solution to this potentially frustrating issue...there are a few things I did to make sure that when any of my pages with text entry fields loaded, the cursor in the text entry field was in focus.
1. Make sure that the text entry item on your timeline (e.g. Text Entry 1) is the first thing at the bottom of your timeline.
2. If you have any background images on your timeline (e.g. screenshot of the software you are developing training for), put that image on a masterslide layout, delete the actual image from the slide itself, and use the masterslide layout with the image on it instead.
3. Finally, Alt text. Make sure no other items on the screen are "visibile to accessibility tools". Only the text entry field should be visible to accessibility tools (including any objects on the master slide).
In my experience, these 3 things have solved this issue for me. Hopefully it works for you and saves you a lot of time and frustration!
Cheers,
Sanjay
Many thanks for stopping in to share your discoveries, Sanjay! Hopefully that will assist many others in the future who come across this post seeking assistance. :)
1607:1221 doesn't seem to fix it for me. If the text entry field is the only field into which a user can enter data, then it should automatically gain the focus. How hard is that?
Hi Perry!
Would you be able to share your .story file or sample slide for us to take a look?
I’m evaluating Storyline 2 on behalf of a client, who’s asked me to build a simple demo to show some of its capabilities. See attached.
Hi Perry!
Not sure if you responded via e-mail, but there is no attachment to your post. Please pop into the forums and utilize the 'Add Attachment' option in the bottom left of the reply window.
Yes, I used Outlook. The REPLY button tried to invoke 365 and I ended up with a Metro view, which I don’t use. I’ll use the forum, as suggested.
Thanks Perry :)
Here it is.
Thanks for the details and for sharing Perry. Looks like our QA Team is looking into some similar reports. I will add this thread for their awareness and so that we can update here when applicable.
Hi Leslie,
So it means that this bug wasn't fixed in a previous update after all right?
In a step-by-step test with screen recording when splitting into slides it didn't split the one with text input. I copied the previous slide, adjusted the timeline and added a data entry field but it just doesn't focus when I preview.
Already changed tab order and timeline. The field cannot be the first at the bottom or it will be below the recording.
Any idea when this will be fixed?
Most of the times when I copy a field that is in focus from another project it works.
Really strange behavior.
Hi Maria!
We did have an issue that was corrected in Update 5. I'm not sure if this is a new issue or same issue, but that's why I've shared with the QA Team.
I do not have a timeline to provide on this issue.
Hi Leslie,
Your reply before mine was posted 15 days ago saying the QA team is looking into this.
My issue is the same as the OP but the text entry field is on a screen recording and not screen shot. I further explain the situation in my previous post.
The issue is the same that is said to be solved in update 5. It is not, or not completely at least.
Please re-read OP and my previous comment and let me know if you still have questions.
Thanks!
I understand Maria.
You are correct - I've shared with the QA Team because it is an issue we thought to be resolved.
Thanks Leslie!
Could you update this thread when it's fixed? I've subscribed.
It is attached to the report for update when applicable, but I do not know any timeline.
I have tried these fixes in Storyline 2 and in 360 and I cannot get the text entry box to autofocus. This is very urgent for a simulation we are creating. Please can you help. I have also tried adding javascript to autofocus it but nothing has worked yet.
Hi Stephanie,
The work around I use is to copy a text field that is in focus from another course and just format the color, outline, etc.
I know this is not ideal and it can actually be a lot of work, so I hope a fix for this is patched soon.
Good luck.
Hi Maria,
Thanks for replying but unfortunately none of my courses have a text field in focus. It works in preview but does not in export.
Hi Stephanie - I do not have an update to provide on this issue as it is still in the hands of our QA Team, but I have updated to reflect that another user has been affected and perhaps we can get this prioritized in our internal conversations.
This discussion is closed. You can start a new discussion or contact Articulate Support.