Forum Discussion

CHRISTINEWEA135's avatar
CHRISTINEWEA135
Community Member
2 months ago
Solved

Text Entry box help

I've created a simulation (screen recording) where a user logs into a page. They have to enter certain fields like a workspace name, address etc... I need them to type it exactly as desired, so I have it set up like a quiz question.

We are providing no feedback, as we want the learner to feel like they are in our actual program, which does not tell you if you're correct or incorrect. You type in the box, hit enter on your keyboard and if it matches, it should move to the next slide. If not, it stays and nothing happens. 

Problem #1- while in preview mode, when I type in the box, I see no text of what I'm typing. I have no idea if I've made a typo. How can I have the user see what they are typing as they type it?

Problem #2- it doesn't move forward when hitting enter on keyboard. I have programmed the question for submit on "enter". No submit button. 

I used to create interactions like these in Captivate with my eyes closed but cannot figure out how to do this and I've watched videos, read the blogs. I just want the learner to see their text while typing it in, and to hit Enter. If it is good, it automatically goes to the next slide. If not, it stays on the same screen.

Any assistance would be great. 
Thank you.

  • Hmmm okay something is wrong and it starts with the TEB not showing the text I am typing or capturing it. I decided to start simple. Have a correct/ incorrect layer, as well as a submit button. It doesn't matter what I type in, I get a message (not even one I put in my layers) that I need to complete the interaction. So, this means the TEB itself is not capturing what is being typed in order to validate it.  Alright this is progress. Next step- remove TEB, and re-insert and configure fresh. 

8 Replies

  • The interface you're simulating really doesn't respond in any way if someone enters an invalid Workspace name? By today's standards, that's considered poor design, isn't it? Even a "could not find that workspace" is warranted. 

    Problem #1 is interesting since usually the text shows up. Easy question, but I don't suppose the color of the text is the same as the background, and thus "showing up" but imperceptible to us?

    The screenshot you uploaded shows a trigger that submits "When the user clicks Workspace Text" instead of "When the user presses Enter [...]" so if that's accurate, that'll be the hold up.

  • Thank you for responding,
    While I agree, poor design, we have a lab guide and we are simulating, just for this module, as if they were using the actual application. So not much of a choice for the first exercise. We do have a show me and guide me, that prompt users. It's squirrely for sure- but required.

    I don't really have an option in the drop-down for When the user clicks... Enter is not an option. I can select "Submit button", but I do not have a submit button.  The font is black, against the white background, so I'm still not sure why it is not showing up.

    • AndrewBlemings-'s avatar
      AndrewBlemings-
      Community Member

      For sure, no criticism of you. Just strange for the modern interface you're simulating to not provide user feedback. It's a missed opportunity is all, and I know from experience it's annoying to have to deliberately simulate less-than-ideal design.

      When you're looking at the trigger wizard, your When should be: "When the user presses"

      In web terms, clicking only refers to computer mice, so a trigger of "when the user clicks on the Enter key" could never be true.

      There are a lot of trigger actions and events and conditions, so familiarity will take time. Seems like you're already in a good headspace to get there though!

    • AndrewBlemings-'s avatar
      AndrewBlemings-
      Community Member

      I sent it before I added the conditional. To add a lock to this metaphorical door, you wanted to check the value of the entered text. You'll need to click down in the Conditions section to find the input field's text variable, and then type in the value it checks against.

      If the learner presses enter and the entered text matches your template answer, the course will jump to the next slide. If the text doesn't match in any way (including a trailing space), the course will do nothing.

  • Hmmm okay something is wrong and it starts with the TEB not showing the text I am typing or capturing it. I decided to start simple. Have a correct/ incorrect layer, as well as a submit button. It doesn't matter what I type in, I get a message (not even one I put in my layers) that I need to complete the interaction. So, this means the TEB itself is not capturing what is being typed in order to validate it.  Alright this is progress. Next step- remove TEB, and re-insert and configure fresh. 

    • AndrewBlemings-'s avatar
      AndrewBlemings-
      Community Member

      From a non-newbie to a non-, I'd avoid the whole quiz slide thing for now if I were you. Quiz slides bring a whole of additional functionality and "logic" to make quizzes easier for us, things like keeping track of which wrong answers were selected, the percentage of right answers, how many points each question is worth, and so on.

      And that's great when building an actual structured assessment, but since what you want is simply an ungraded, type-text-here-to-continue gate, you don't need or want quiz slides. The Submit button it's throwing into the mix has confused many designers on its own, and if your goal is to reproduce the actual production system, this non-quiz implementation is probably your cleanest bet: Text Entry | Review 360

      * The project file is downloadable from the "Current Version" button in the upper-left. The required text is simply the shorter "Hewlett"

       

  • I figured it out! It is a quiz question. The issue with text not appearing didn't happen if I just previewed the single slide. But if I previewed the scene, it wouldn't appear. Anyway my solution:
    Clean the slide up- no triggers nothing just the background image. Change to freeform text entry box. Enter in the required text, and make it submit on key entry of Enter. On the correct layer, remove all text, set the master slide to blank. But add trigger that on start of timeline, jump to next slide. So if they got it right- it moved on.  On incorrect, make it blank- no triggers. So nothing happened if they got it incorrect (on their view).  On Try again layer, hide all text, and set background to blank and add trigger "Hide this layer, when timeline starts on Try again". Okay now they are in a loop if they get it wrong bc they have unlimited attempts.  So, if they get it right- Correct layer just moves them on. If they get it wrong, incorrect doesn't matter bc unlimited attempts and it takes them to try again layer. Try again layer just hides upon entry of timeline. WHEW!

    • AndrewBlemings-'s avatar
      AndrewBlemings-
      Community Member

      That's what I mean, haha. Adding formal Quiz slides in Storyline brings a bunch of extra stuff like feedback layers, which you and I can create manually using the basic tools of Storyline, but can be expedited by adding official Quiz slides. In simpler projects though, that extra stuff becomes baggage.

      If you check out what I linked in the other comment, it accomplishes what you want without adding a bunch of stuff and then turning around and deleting it. If you're hiding all of the content on the feedback slides and hiding the feedback slides as soon as they show, then why add the feedback slides in the first place?