Survey textbox element crashes Inquisit


Survey textbox element crashes Inquisit

Author
Message
Loukia
Loukia
Esteemed Member
Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)

Group: Forum Members
Posts: 22, Visits: 376
Hi, 

I have a number of 'radiobuttons' elements on a survey and the 'other' option is defined as a textbox element. No matter what parameters are used for the textbox element [e.g., /mask = alphanumeric; /validresponse = (anyresponse)], after typing a few letters or the spacebar being pressed or sometimes just clicking on the cursor inside the textbox, inquisit crashes completely. I don't see an error in the messages later or warnings, it just closes completely. 
Is this a reported bug with textbox elements used as 'other' responses or would there be an obvious reason this is happening in terms of the code?
This is happening with both lab and online settings.

I have attached the script. See line 213- <textbox gender_other> for example textbox that causes a crash. 

Thanks a lot in advance.
Attachments
eligibility_survey.iqx (409 views, 27.00 KB)
Loukia
Loukia
Esteemed Member
Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)Esteemed Member (1.8K reputation)

Group: Forum Members
Posts: 22, Visits: 376
Hi Dave, 

I found the issue and I thought I would report it for future users of the /quitcommand parameter in the <defaults> element. In my main script that includes the survey I specified /quitcommand = (56 + 30). In contrast to what the manual suggests, the words Ctrl and Alt don't work at all ('not valid') so I used the scancode for 'Alt' which is 56.

I figured this was the issue since the crash happened only when I typed the letter 'A'. It seems the quit command was interpreted as the 'A' key only. I have removed the quitcommand completely and it runs perfectly- no crashes so far. However, I need to specify a different quit command so that when the participants want to quit they go to the finish page, instead of simply quiting the program. What are combinations that work in the /quitcommand, if the command keys are not considered valid anymore? 


GO


Reading This Topic


Login
Existing Account
Email Address:


Password:


Social Logins

Select a Forum....






Millisecond Forums


Search