Step-by-step Try mode - Text Entry issue
I would expect for the screenrecording Try mode to provide a realistic end-user experience of a process. There are 2 concerns. In this example, I've recorded a 'Logging in' lesson.
The first issue is that when a user clicks the 'User Name' box in the first slide, they can't type their user name on the second slide. It's because when the second slide appears, the cursor isn't active in the text box. The user has to click in the text box a second time before typing.
The second issue is that, by default, the user needs to press Enter after entering text in order for the Try mode to verify what they've entered. This is problematic because if a user were to press enter after entering a username in the real world, they would get an 'incorrect username/password' error. (we've seen users do this in the past after having completed unrealistic simulations)
For the second issue, you can somewhat get around it adding hotspots onto each text entry frame, adjusting the triggers, and deleting the now-redundant following frames but you still subsequently encounter the first issue. Also this adds a significant amount of development time for each text entry you record.
Anyone else encounter or resolve this?