Forum Discussion
Storyline Text Entry Marked as Incorrect When Pressing Enter Button
Hello!
I am currently using text entry in storyline. There is a submit button. When you enter the text and press the submit button on the screen it is marked as correct. But when you enter the same text and press the enter button on your keyboard it is marked as incorrect.
Does anyone have any idea why this is?
Here are the triggers:
Here are the variables:
Any help would be very much appreciated!
Here are my settings incase anyone else in the future is reading this post.
- RonPricePartner
If you use Storyline's Quiz feature, it will do most of the work for you. Therefore, unless you want something pretty custom, you just fill out the form in Form View. In your case, you type in the acceptable answer "internal" and then check that it is not case-sensitive and it should work without any additional triggering from you.
So, the triggers inside the square in this graphic are not even needed:
- TanyaThampip494Community Member
Thank you for notifying me of this! I completely forgot to check the form view. I have updated my settings, and it works beautifully!
- RonPricePartner
Did you build the "set correct answer . . ." Triggers?
I do not think those should be necessary.
- TanyaThampip494Community Member
Should I delete them? Does storyline already have one? I'll look into this in the meantime.
I used the built-in variable: Question.Correct and it still does not work.
- TanyaThampip494Community Member
Here is an example to further explain what I mean in articulate review: https://360.articulate.com/review/content/37a34fdc-e8f1-4962-914e-193f564e7dda/review
The correct answer is internal, INTERNAL, or Internal. - TanyaThampip494Community Member
This articulate article says the enter button and submit button should behave the same but they do not.
https://community.articulate.com/discussions/discuss/storyline-text-entry-marked-as-incorrect-when-pressing-enter-button/1202172/replies/1202198 - TanyaThampip494Community Member
Here are my settings incase anyone else in the future is reading this post.