I created a screen recording and set it up in test mode. When I input text during the screen recording it doesn't show up as a text box in the edit mode.
How can I add a text box for the learner to write in when one isn't being created for me?
I looked on-line searching for the answer. I came across videos etc but nothing answered my question above.
Hey Ellana! I was actually just doing some investigating on this issue. I'm trying to find out why the text entry didn't populate onto that slide for you. Did this happen with other or all text entry slides, as well?
There are rules that Windows apps have to follow in order for Storyline screen recordings to pick up on keystrokes and clicks, but I'm researching for a better understanding of them.
Have you tried re-recording the scenario? I'm not sure if that is a viable option for you, for testing. But I'll update this thread as soon as I get some additional info!
Hi again, Ellana. I was able to replicate this issue in a screen recording that I made when using different applications. Some of my text entries were available, some were not.
As far as the "rules," this is the information that I discovered: Certain apps and programs, when written, may have included "accessibility" features within their controls. If the processes that you perform with that app are not accessible to Storyline, they won't be picked up in the step-by-step modes of screen recording. Most apps are moving away from controls that would prevent Storyline from recognizing keystrokes.
That being said, we'd be very happy to take a look at your project, or your screen recording, at least to see if we can test further or help develop a workaround. Also, if your screen recording is of an application that we can install and test, we can try that as well.
Also, Ellana, this article explains how Google Chrome actions are not recorded accurately in Storyline screen recordings, in case that is what you are capturing.
7 Replies
Hi,
Does anyone know the answer to this?
Thanks
Ellana
Hey Ellana! I was actually just doing some investigating on this issue. I'm trying to find out why the text entry didn't populate onto that slide for you. Did this happen with other or all text entry slides, as well?
There are rules that Windows apps have to follow in order for Storyline screen recordings to pick up on keystrokes and clicks, but I'm researching for a better understanding of them.
Have you tried re-recording the scenario? I'm not sure if that is a viable option for you, for testing. But I'll update this thread as soon as I get some additional info!
Hi Crystal,
Thank you for looking into that. It happens for all text entry slides. I wonder if its the software I'm using.
Yes I have tried it a few different ways and typing in to different areas of the software but it still doesn't show up as a text entry.
Thanks!
Hi again, Ellana. I was able to replicate this issue in a screen recording that I made when using different applications. Some of my text entries were available, some were not.
As far as the "rules," this is the information that I discovered:
Certain apps and programs, when written, may have included "accessibility" features within their controls. If the processes that you perform with that app are not accessible to Storyline, they won't be picked up in the step-by-step modes of screen recording. Most apps are moving away from controls that would prevent Storyline from recognizing keystrokes.
That being said, we'd be very happy to take a look at your project, or your screen recording, at least to see if we can test further or help develop a workaround. Also, if your screen recording is of an application that we can install and test, we can try that as well.
Also, Ellana, this article explains how Google Chrome actions are not recorded accurately in Storyline screen recordings, in case that is what you are capturing.
Hi Crystal,
Thank you so much!
You were right the problem was that I was using Google Chrome. IE worked just fine.
Thanks!
Ellana
Awesome! I'm glad that worked for you. I have to thank my team for digging up that article! :)
This discussion is closed. You can start a new discussion or contact Articulate Support.