Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

[solved] Keyboard Response unresponsive

edited April 2014 in OpenSesame

I'm trying to create a script for a self-paced reading experiment. I've started by creating a single trial but I've encountered some strange behaviour. The trial sequence involves a series of Text Displays, each separated by a Keyboard Response (participants press space after reading the word presented on each display). Originally I had five displays and noticed that after the fourth display you have to press space twice to get to the fifth display. I experimented by adding a sixth display and found that after this I again have to press space twice to get to the final screen.

I've looked at the code and I can't see any difference between those responses (and the displays that precede them) that work with one press (chunks 1-3 & 5) and those that require two (chunks 4 & 6).

Here is my script: http://pastebin.com/vd6enxy4

Comments

  • edited April 2014

    I tried running your experiment, and it seems fine to me! (Ubuntu 12.04, OpenSesame 2.8.1)

    Please do note that you run the same Text Display, chunk_6, twice in a row. This means that although you are pressing a key, the screen will remain the same.

    A similar principle is true for chunk_3 and chunk_4. Those are different items, but they have the exact same contents ("a")

    If this is not the source of the double clicks, please do report back! (in that case, it would be useful if you mention your operating system, as well as the version of OpenSesame you are running)

  • edited 12:52PM

    I have no idea how chunk_6 ended up being run twice, but thanks for pointing out my mistake with chunk_3 and chunk_4. It's all working fine now!

Sign In or Register to comment.