Hi Ahmed, After some troubleshooting I realized that the "jQuery('#NextButton').click();" from the introductory page (where the page moves forward with the press of a key) was carrying forward to the other words.I gave your suggestion a try and it seems to work but the options disappear after a keypress. Thank you for your help. I will have to fiddle around with the design to make sure this will work on a larger scale, but you've pointed me in the right direction. I also ended up changing the script slightly per word so I'll test a few variations of the original script out with your suggestion as well: Qualtrics.SurveyEngine.addOnload(function () { let questionTime = 3 // The number of seconds the question is to be displayed for. this.hideNextButton(); var that = this; (function(){ that.clickNextButton(); console.log('NEXT BUTTON'); }).delay(questionTime); var startTime = new Date().getTime(); var that = this; Event.observe(document, 'keydown', function keydownCallback(e) { var ch
Hi Ahmed,Apologies, here is the task in detail:In total, the task must last 5.6 minutes where there are 20 unique blocks that are pseudo-randomized.each block contains a condition screen + 5 words.there are 2 conditions: participants are asked if each word describes themselves or if the word is upper case.Words are randomized to appear as either uppercase (e.g. ALIVE) or lowercase (e.g. Alive).Words are also either positively or negatively valenced, e.g. Alive (positive) vs Afraid (negative). Each grouping of 5 words will have the same valence.Altogether, participants should see all conditions, all uppercase/lower case versions of each word, and an equal amount of valenced wordsI have used branching, embedded data and randomization in the survey flow to ensure participants are seeing all possibilities in a block-randomized orderThe issue:As the task must be the same length for everyone, I'd like to code it such that participants can press either "g" for "yes" or "h" for "no" as soon as
Hi Ahmed,Oh, I missed the break line. Thank you for pointing that out! I think you are right in that the setTimeout may not be accurate. Is there something in the keypress syntax that can prevent a keypress from triggering the page to automatically move forward again?Qualtrics.SurveyEngine.addOnload(function () { var startTime = new Date().getTime(); var that = this; Event.observe(document, 'keydown', function keydownCallback(e) { var choiceID = null; switch (e.keyCode) { case 71: // '1' was pressed choiceID = 1; setTimeout(function() { jquery('#NextButton').click(); }, 3000); break; case 72: // '2' was pressed choiceID = 2; setTimeout(function() { jquery('#NextButton').click(); }, 3000); break; } if (choiceID) { let rTime =new Date().getTime() - startTime; Event.stopObserving(document, 'keydown', keydownCallback); that.setChoiceValue(choiceID, true);Qualtrics.SurveyEngine.setEmbeddedData('DAliverTime', rTime); } });});In terms of the conditions,
Hi Ahmed,Your survey flow was very helpful and I can see the main idea. I was thinking of branching and using embedded data too. I'll play around with this format and give this some more thought over the next few days. Does this also account for the fact that each block in each condition will be viewed by all participants and that they will only see one condition once?
Thank you for the response. If I followed the main idea survey flow, is there any way to ensure participants will see all blocks at some point but never see the same block again?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
