Text Entry Allowable Characters - HELP

Oct 18, 2018

I noticed that the text entries that include a special keyboard character like > doesn't seem to be recognized when the question is processed. The $ and ! are fine.

Is an underscore accepted? If I copy/paste into the field, the entry with an underscore is accepted. If I type it in, as I'm asking learners to do, I'm told the entry is wrong.

Is this true? If yes, is there a way around it? 

I have sort of a system simulation set up in my course where the learner types in a command, usually involving a password or other entry with special characters found on a typical keyboard. 

And of course, I'm pushing a deadline.

10 Replies
Alyssa Gomez

Hello, Jan! Happy to help you sort this out.

I created a quick sample file with two text entry questions. One has > in the answer, and the other has _ in the answer.

From my testing, it looks like Storyline accepts those characters without any issues.

Could you also test these two slides and let me know if it works well for you, too?

Jan Brooks

Thank you, Alyssa. Yes; these worked just fine.
I have a support ticket in place and uploaded my title.

Did you do anything special on these examples?
I wonder if maybe my page is corrupted and I just need to redo it. ---Update - that wasn't it. Ugh

What happens when you enter this as the correct answer? open rand –ex 123 >  text_file.txt

Alyssa Gomez

Thanks for also opening a case, Jan! I see Jonathan is already reviewing your project file.

The sample I shared with you was built with simple freeform text entry slides -- nothing special! 

Let's be sure you and I are both testing on the same version of Storyline 360. To check, click the Help tab, then click About Storyline. You should see 3.20.16814.0 in the bottom-right corner. 

Jan Brooks

Jonathan figured it out! Way to go, Jonathan!!

The problem is that - just like Word, PowerPoint, etc - when you type a hypen and a word to follow, and then press space again, the hypen becomes an en-dash. I never expected this would happen in the question form where I'm entering a correct answer, but it did! 

Fortunately, the hyphen isn't converted when a learner completes the field. 

To fix the problem, I went back to the form, deleted the hypen, and then added it back (without retyping the full entry or pressing the space bar).  

Please be sure to add this to the bug fix list!!

Thank you for following up on this! Articulate Support and Communities are the BEST!

This discussion is closed. You can start a new discussion or contact Articulate Support.