Keyboard responses: Set Timeout to defined variable doesn't work in OSWeb

joshmanu

Hi,

question about OSWeb & keyboard responses

In the keyboard_response item I would like to set the 'Timeout' to my variable 'duration' (defined in my block loop). Thus replacing the default value 'infinite' to: "[duration]". Thereby showing the stimulus on the preceding sketchpad (which has a duration of 0) for a duration equal to that variable. This works fine when running the file in Opensesame, but when running the script in the browser, the stimulus does not disappear after the 'Timeout' duration, it will only disappear after a keypress.

If I set the 'Timeout' to 1500 (instead of '[duration]') everything works fine in OSWeb.

I was wondering what goes wrong here...

I am running Opensesame version 3.3.1 on Linux & OSweb version 1.3.8.2.

Working example:

keyboard_test.osexp

Thank you!

Josh

pinarke

Hi,

I am facing exactly the same problem for touch responses.

Similar to Josh's, when I set Timeout to one of my variables (e.g., [time1]), the preceding sketchpad remains on the screen until the participant clicks (as if I set the timeout to infinite).

I thought the solutions would be similar, that's why I did not open a new discussion for that. I would be very happy if someone has an idea to fix it or find another way to do that.

Thank you very much,

Pinar

Daniel

Hi both. I remember this to have been a reported bug, but I am not sure if it is fixed. Opensesame is at 3.3.3 at the moment which also has a new version of osweb. Could you try upgrading to that and see if the bug still occurs?

pinarke

Hi Daniel,

Thanks for your reply. I am using OpenSesame 3.3.3 and OSWeb 1.3.8 versions (on Windows), and unfortunately it still doesn't work.

Do you think there could be a workaround for this by including a js code somewhere in the experiment? (e.g., is there a function to force the response item to stop when a specified condition occurred (when current time stamp - time_preceding sketchpad = [my_variable], for instance?) I'm not sure if this makes sense; but if you have any other idea to workaround this sitation, I will be more than appreciated.

Thank you very much,

Pinar

marsaute

@Daniel I have the same problem. There's a bug report already out.

https://github.com/open-cogsci/osweb/issues/27

This issue still persists and also affects advaced_delay items.

Can anyone think of a workaround?

omar_escamez

Hello! I have been trying these days to solve this issue as well and I have found a different way that also seems to work.

The problem:

The idea is that when you have in the same sequence 1) the inline with the variable (and its value) and 2) the keyboard with the timeout defined using that variable, it does not behave the way it should.

The way I have solved it:

In the same sequence that I have described above, instead of place a keyboard directly at the same level, I introduce a loop with a new sequence. In this new sequence I only introduce the keyboard.

Note: When the variable you use for the keyboard has a value less or equal to 0, it does not work. If this is the case, you can set the 'Run if' of the loop (with the keyboard) when the value of the variable is higher than 0.

I hope it could help!