I am using SL2 to create a software simulation. I have tested it in all 3 modes View, Try, Test and they all seem to self populate the text entry fields. The only interaction that seems to get recorded is the Hotspot.
This is a web-based app that I am recording and I am using IE to use the app. I have done this before successfully with SL. Is there something I am missing?
View should include what you type as a part of the playback, and Try and Test modes should allow you to enter some text prior to showing you what was entered on the next screen.
You mentioned using IE to record the app, which is good as it does capture more info than a browser such as Chrome. Have you recorded this same app before? It could be a good test to try recording something else such as just google search or something similar with typing to see how that translates in the screen recording.
Let us know if you need any other help, and then we'd want to take a look at your .story file!
Thanks. I have never recorded this app before so I thought I would try something simpler to test. One more thing though...I was having the same problem with a .pdf file running JavaScript for the fields. Does JavaScript conflict in anyway? Thanks again for the help.
It's a PDF form that the learner has to populate. It records the hotspots but it doesn't record any text entry. It self-populates with what I hoped would be recorded and doesn't allow the learner to enter any text. I have found another way using text boxes and variables to keep score, but it would be a lot simpler (faster) if I could record the simulation.
Hi there, Andrew. I'm sorry you had to use a workaround. It sounds like not all of the information of that application, or the PDF reader, at least, is being communicated to the screen recording tool. We have one other instance of this behavior documented, so I'm going to add your details to that report.
If there are any other workarounds or changes, we'll keep you updated right here.
5 Replies
Hi Drew,
View should include what you type as a part of the playback, and Try and Test modes should allow you to enter some text prior to showing you what was entered on the next screen.
You mentioned using IE to record the app, which is good as it does capture more info than a browser such as Chrome. Have you recorded this same app before? It could be a good test to try recording something else such as just google search or something similar with typing to see how that translates in the screen recording.
Let us know if you need any other help, and then we'd want to take a look at your .story file!
Thanks. I have never recorded this app before so I thought I would try something simpler to test. One more thing though...I was having the same problem with a .pdf file running JavaScript for the fields. Does JavaScript conflict in anyway? Thanks again for the help.
Hi Andrew!
Do you mean that you're recording a PDF file, and the screen recording tool isn't capturing the javascript?
If you can tell us a bit more about what you're seeing, hopefully we can point you in the right direction. 😊
It's a PDF form that the learner has to populate. It records the hotspots but it doesn't record any text entry. It self-populates with what I hoped would be recorded and doesn't allow the learner to enter any text. I have found another way using text boxes and variables to keep score, but it would be a lot simpler (faster) if I could record the simulation.
Hi there, Andrew. I'm sorry you had to use a workaround. It sounds like not all of the information of that application, or the PDF reader, at least, is being communicated to the screen recording tool. We have one other instance of this behavior documented, so I'm going to add your details to that report.
If there are any other workarounds or changes, we'll keep you updated right here.
This discussion is closed. You can start a new discussion or contact Articulate Support.