OSWeb keyboard responses
Hi all,
I have created a task that uses keyboard responses which works fine when running it normally, however when I try to run it in OSWeb, the keyboard responses seem not to get registered.
In the task, stimuli are shown through a sketchpad with a duration of 0, after which a keyboard response with a certain timeout is placed. It looks somewhat like this:
Sketchpad1 (duration=0) ---> Keyboard response1 (Timeout=495) ---> Sketchpad2 (duration=0) ---> Keyboard response2 (Timeout=495) ---> Sketchpad1 (duration=0) ---> Keyboard response1 (Timeout=995) ---> Feedback.
On my pc, the correct feedback item is shown when the sequence finished or as soon as the space bar is pressed. When pressing the space bar In OSWeb however, the sequence still finishes completely after which the feedback acts as if nothing was pressed.
Does anybody know what might cause this?
Cheers,
Boris
Comments
I have found the problem! I had "space" as the allowed responses, and for some reason leaving it empty fixed the issue.
Hi Boris,
I have a similar problem with the keyboard response. I tried to use "space" as response key but it is not working.
I tried it also in the off-line mode and it is working fine.
Do you have any suggestion?
With the new version of Opensesame 3.3 the key "space" problem is solved.
Hello everyone,
Is there any possibility to record time stamps for individual key presses? Unfortunately I can not rely on OS response-time calculation and would want to use an own procedure instead. The log does not seem to contain the keypress timestamps (or am I reading it wrong?).
Hello Art,
normally OS is taking time stamps for all the items that are called, including the keyboard response and response items. If I am not mistaken the variable is called
var.time_response. To compute response time, you also need a reference point, which should be calledvar.time_keyboard_item.Does that make sense?
Eduard
Eduard,
This is exactly what I needed.
It wasn't obvious to me when looking at the log file but now is clear.
Thanks a ton!
I figured out that the use of the space key evokes some strange and very small scrolling in the browser (at least in Chrome). Maybe it has to do with the upper problems?