Character Limit on Text Input strings?

Jan 02, 2023

I'm working on this never ending project and in the practice session, the user has to type a fairly long character string that has a space in it into a text entry field. I cannot get the trigger to cooperate. I have it set so when the string is typed correctly, when the user presses ENTER, the slide jumps to the next slide. If they fat fingered, a layer pops up telling them to check their typing. I've done the very thing on a bunch of other slides but this slide is giving me fits. It has been popping the error message even when it's correct. I deleted the error message trigger and pressing ENTER does nothing. 

I can't get this to work. Is there a character limit, or issue with the space in the string? Any suggestions for a workaround? I've attached the slide before and after in the file below.

Thanks for any insights. 

problem slide

7 Replies
Sandeep Gadam

Hi there, I reviewed your file and I couldn't find any issue in moving forward with it while in preview mode. Everything works just fine. But once I publish as web output, it acts strange. Initially it worked fine and when I keep on trying, at some point I'm able to replicate the specified issue. But in most attempts I couldn't replicate the issue.

Jean Marrapodi

Hi Sandeep and thanks for trying. I'm finding that it's being really inconsistent. I'm not sure if it's the length of the string or what. I don't think it's the space, since I have another that is 2 characters, space, 2 characters and it's fine.

In your above comment, did you replace the text with the same long string? I did that and found it worked once but not again. This is so peculiar!

For now I'm going to eliminate checking the typing and give the user the benefit of the doubt and let them click ENTER to move forward.  It is puzzling for sure. 

Sandeep Gadam

HI Jean, Yes, I have entered the same long string "/opt/ipc/cop/ksrecop/./recop54.sh 10.201.207.198" both manually and copy paste and it worked fine on the first attempt. So I cleared the browser cache and gave it another try and then I replicated the specified issue. This occurred to me while I kept trying continuously. I wish someone could help you find a way to overcome this issue.

All the best!!!

Steve Gannon

Jean,

Your keypress triggers are looking for "...206..." in the entry but you have indicated it should be "...207..." When I preview and also when I publish, "206" seems to work correctly for me every time (i.e., it advances to the last slide). An entry with "207" always generates the error message as I would expect.