|
Gaurav Krishnamoorthy
|
|
|
Group: Forum Members
Posts: 9,
Visits: 27
|
Hi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help!
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 13K,
Visits: 105K
|
+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred.
|
|
|
|
|
Gaurav Krishnamoorthy
|
|
|
Group: Forum Members
Posts: 9,
Visits: 27
|
+x+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred. Thank you so much Dave. We thought as much for #2. Just wanted to make sure as there was some uncertainty.
|
|
|
|
|
Gaurav Krishnamoorthy
|
|
|
Group: Forum Members
Posts: 9,
Visits: 27
|
+x+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred. Thank you very much Dave, your answers are very helpful. In regards to Answer #1, we did change timeout for trialduration to make sure the timing is fixed. We coded the trial b1, so that b1 (the image a letter) would appear at 500ms and coded the trial b0 (blank image) so it appears at 1000ms. The end result of these two stimuli, is that the letter image (b1) appears at 500ms and disappears at 1000ms. Our initial concern is the timing between trials. We noticed that when participants respond to the stimuli (image letter) before it fades out at 1000ms the next trial appears right away (even though I changed it to "trialduration"), it does not wait until the actual timing of the entire trial ends. Do you have any suggestions on how we could change this fact? We don’t mind when the participant responds to the trials but we do care, on keeping fixed timings of the trials, so that whenever the participant answers it does not automatically skip to the next trial. Thank you for all your help,
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 13K,
Visits: 105K
|
+x+x+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred. Thank you very much Dave, your answers are very helpful. In regards to Answer #1, we did change timeout for trialduration to make sure the timing is fixed. We coded the trial b1, so that b1 (the image a letter) would appear at 500ms and coded the trial b0 (blank image) so it appears at 1000ms. The end result of these two stimuli, is that the letter image (b1) appears at 500ms and disappears at 1000ms. Our initial concern is the timing between trials. We noticed that when participants respond to the stimuli (image letter) before it fades out at 1000ms the next trial appears right away (even though I changed it to "trialduration"), it does not wait until the actual timing of the entire trial ends. Do you have any suggestions on how we could change this fact? We don’t mind when the participant responds to the trials but we do care, on keeping fixed timings of the trials, so that whenever the participant answers it does not automatically skip to the next trial. Thank you for all your help, Again: To fix the duration of a <trial>, use /trialduration. Display of stimuli by the trial is a different issue. If you have <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 ... </trial> and a response occurs prior to b0, the stimulus presentation sequence will terminate. The trial will *still* last as long as specified in /trialduration. If, in addition, you want the trial to *complete* its stimulus presentation sequence *despite* a response having already occurred, you need to make use of the /responseinterrupt attribute: <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 / responseinterrupt = frames ... </trial>
|
|
|
|
|
Gaurav Krishnamoorthy
|
|
|
Group: Forum Members
Posts: 9,
Visits: 27
|
+x+x+x+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred. Thank you very much Dave, your answers are very helpful. In regards to Answer #1, we did change timeout for trialduration to make sure the timing is fixed. We coded the trial b1, so that b1 (the image a letter) would appear at 500ms and coded the trial b0 (blank image) so it appears at 1000ms. The end result of these two stimuli, is that the letter image (b1) appears at 500ms and disappears at 1000ms. Our initial concern is the timing between trials. We noticed that when participants respond to the stimuli (image letter) before it fades out at 1000ms the next trial appears right away (even though I changed it to "trialduration"), it does not wait until the actual timing of the entire trial ends. Do you have any suggestions on how we could change this fact? We don’t mind when the participant responds to the trials but we do care, on keeping fixed timings of the trials, so that whenever the participant answers it does not automatically skip to the next trial. Thank you for all your help, Again: To fix the duration of a <trial>, use /trialduration. Display of stimuli by the trial is a different issue. If you have <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 ... </trial> and a response occurs prior to b0, the stimulus presentation sequence will terminate. The trial will *still* last as long as specified in /trialduration. If, in addition, you want the trial to *complete* its stimulus presentation sequence *despite* a response having already occurred, you need to make use of the /responseinterrupt attribute: <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 / responseinterrupt = frames ... </trial> Hey Dave Thank you so much Dave! I have tried to incorporate " /responseinterrupt=frames “, but it didn’t change the fact that the trial didn’t complete its stimulus presentation sequence “despite” a response having already occurred before b0. Any suggestions? Thanks so much
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 13K,
Visits: 105K
|
+x+x+x+x+xHi, We are having 2 issues regarding our test and we would like some help on resolving them.
1-We are encountering a problem regarding response times of each trial. As soon as the participant answers, the trial ends abruptly and is succeeded immediately by the next trial. We don't want the next trial to start immediately after response, but rather we want it to start after each specific timeframe as indicated by the trial's specific "timeout".
2-We are also experiencing issues regarding the registered answers from participants. We want our test to take the first response only, and disregarding the possibility of other additional response inputs by participants.
Here is a sample of how we coded our trials. Thanks! ... <trial b1> / stimulustimes = [500=b1;1000=b0] /inputdevice=keyboard /correctresponse=("a") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2100 / recorddata = true / ontrialend = [ if (trial.b1.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b1.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b1.error) values.losses1 +=0] / ontrialend = [ if (trial.b1.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<trial b2> / stimulustimes = [500=b2;1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /timeout=2700 / recorddata = true / ontrialend = [ if (trial.b2.correct) values.earnings1 +=0.5] / ontrialend = [ if (trial.b2.error) values.errorcounter1 +=1] / ontrialend = [ if (trial.b2.error) values.losses1 +=0] / ontrialend = [ if (trial.b2.error && values.errorcounter1 > 1) values.losses1 -= 0.5]</trial>
<values > /earnings1=0 /losses1=0 /errorcounter1=0 </values> ...
Thank you for your help! 1) /timeout specifies the *maximum* trial duration, i.e. the trial is *supposed* to end earlier if a response occurs prior to the timeout ending. If you want a *fixed* duration, use /trialduration, not /timeout. 2) I don't understand issue #2. A <trial> -- by default -- only accepts one response. There is nothing in your code that would make the <trial> accept any additional response after the 1st one has occurred. Thank you very much Dave, your answers are very helpful. In regards to Answer #1, we did change timeout for trialduration to make sure the timing is fixed. We coded the trial b1, so that b1 (the image a letter) would appear at 500ms and coded the trial b0 (blank image) so it appears at 1000ms. The end result of these two stimuli, is that the letter image (b1) appears at 500ms and disappears at 1000ms. Our initial concern is the timing between trials. We noticed that when participants respond to the stimuli (image letter) before it fades out at 1000ms the next trial appears right away (even though I changed it to "trialduration"), it does not wait until the actual timing of the entire trial ends. Do you have any suggestions on how we could change this fact? We don’t mind when the participant responds to the trials but we do care, on keeping fixed timings of the trials, so that whenever the participant answers it does not automatically skip to the next trial. Thank you for all your help, Again: To fix the duration of a <trial>, use /trialduration. Display of stimuli by the trial is a different issue. If you have <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 ... </trial> and a response occurs prior to b0, the stimulus presentation sequence will terminate. The trial will *still* last as long as specified in /trialduration. If, in addition, you want the trial to *complete* its stimulus presentation sequence *despite* a response having already occurred, you need to make use of the /responseinterrupt attribute: <trial b2> / stimulustimes = [500=b2;1000=b0] ... /beginresponsetime=0 / responseinterrupt = frames ... </trial> Hey Dave Thank you so much Dave! I have tried to incorporate " /responseinterrupt=frames “, but it didn’t change the fact that the trial didn’t complete its stimulus presentation sequence “despite” a response having already occurred before b0. Any suggestions? Thanks so much With /responseinterrupt=frames, the <trial> will display "b0" -- i.e. complete the presentation -- even if a response already occurred *prior* to b0. That's what it's supposed to do. If -- in addition -- you want b0 to remain on-screen for the entire duration of the trial, you need to make use of the stimulus' /erase attribute: <trial b2> /stimulustimes = [0=clearscreen; 500=b2; 1000=b0] /inputdevice=keyboard /correctresponse=("l") /validresponse = ("a","l") /beginresponsetime=0 /trialduration=2700 / recorddata = true / responseinterrupt = trial </trial> <text b2> / items = ("b2") / erase = false </text> <text b0> / items = ("b0") / erase = false </text> <block myblock> / trials = [1-5 = b2] </block>
|
|
|
|
|
Gaurav Krishnamoorthy
|
|
|
Group: Forum Members
Posts: 9,
Visits: 27
|
Hi Dave! Thank you so much for that last reply. We truly appreciate your help.
We need your guidance once again! We are incorporating a VAS script into our test. Here is what we have coded so far:
... <slider Pain> / caption = "PAIN:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<slider Unpleasant> / caption = "UNPLEASANT:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<slider Noticeable> / caption = "NOTICEABLE:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<surveypage VAS> /caption = "Please indicate the extent to which you the believe each of the following characteristics describe your pain during this session by moving the markers to the appropriate places on the lines below:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) / questions = [1=Pain; 2=Unpleasant; 3=Noticeable] / response = free / itemspacing = 10% </surveypage>
<survey VAS> / pages = [1=VAS] / itemspacing = 10% / recorddata = true / showpagenumbers = false / showquestionnumbers = false / nextbuttonposition = (90,90) </survey> ...
We can’t figure this bit on our own:
1. We want the possibility of having decimal responses…such as 8.34 for example rather than 8 2. We also want to use the keystroke “a” for left and “l” for right to move the cursor on the slider; and so instead of the mouse, we would like for our participants to have the possibility to move from right to left using those keys. 3.How could we change the color of the slider and cursor into black? Our experiment’s screencolor is black, and I was able to change the labels as well as the text to white, except for the slider itself.
Thank you so much Dave, your help is much appreciated!
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 13K,
Visits: 105K
|
+xHi Dave! Thank you so much for that last reply. We truly appreciate your help.
We need your guidance once again! We are incorporating a VAS script into our test. Here is what we have coded so far:
... <slider Pain> / caption = "PAIN:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<slider Unpleasant> / caption = "UNPLEASANT:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<slider Noticeable> / caption = "NOTICEABLE:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) /labels = ("Not at all", "2", "3", "4", "5", "6", "7", "8", "9", "Extremely") / range = (0, 10) / increment = 1 / slidersize = (70, 7) / showtooltips = true / required = false </slider>
<surveypage VAS> /caption = "Please indicate the extent to which you the believe each of the following characteristics describe your pain during this session by moving the markers to the appropriate places on the lines below:" /fontstyle = ("Gill", 2%, true, false, false, false, 5, 0) / questions = [1=Pain; 2=Unpleasant; 3=Noticeable] / response = free / itemspacing = 10% </surveypage>
<survey VAS> / pages = [1=VAS] / itemspacing = 10% / recorddata = true / showpagenumbers = false / showquestionnumbers = false / nextbuttonposition = (90,90) </survey> ...
We can’t figure this bit on our own:
1. We want the possibility of having decimal responses…such as 8.34 for example rather than 8 2. We also want to use the keystroke “a” for left and “l” for right to move the cursor on the slider; and so instead of the mouse, we would like for our participants to have the possibility to move from right to left using those keys. 3.How could we change the color of the slider and cursor into black? Our experiment’s screencolor is black, and I was able to change the labels as well as the text to white, except for the slider itself.
Thank you so much Dave, your help is much appreciated! Neither 1, 2 or 3 are possible with <slider> elements.
|
|
|
|