Conditional variable not read correctly with Tab key
May 28, 2014
I wonder if anyone has an answer to my problem: I'm creating a software simulation in which the student will enter text into a text data field. When the student press their Tab key, a trigger should advance to a certain slide if the text they entered is correct, or advance to a different slide if the text is incorrect. I've written two simple conditional triggers that should work, but they don't. No matter if the text is correct or incorrect, they will always advance as if the text is incorrect.
data field: ClassName1
correct text is: 2014 Anniversary Tickets
Trigger #1
Jump to 4.52 FullClassNameEntry
when user presses the Tab key
if ClassName1 is equal to, ignore case 2014 Anniversary Tickets
Trigger #2
Jump to 4.51 PartialClassNameEntry
when user presses the Tab key
if ClassName1 is not equal to, ignore case 2014 Anniversary Tickets
What am I doing wrong? How can I fix this?
Thanks for any help you can give me. (BTW: I know that the Tab key is used with accessibility tools. I've manually turned off accessibility to all objects that I have entered. I've written other triggers that successfully advance to a slide when the student press their Tab key, but without a condition in the trigger.)
2 Replies
Hi Basia,
This is happening because the value of the text entry variable is not adjusted until the control loses focus so it'll be considered incorrect until the user clicks outside the text entry box or uses the enter key.
Have you looked at setting up a freeform text entry quiz question instead of just adding the text entry to a slide? You could then use the built in feedback branching to determine which slide to go to - and you'll also want to set up an additional trigger to assign the value of the text entry variable based on the user clicking the tab key - and that trigger should appear before the submit trigger.
Interesting. I'll try it.
This discussion is closed. You can start a new discussion or contact Articulate Support.