Howdy, Stranger!

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

Supported by

problems with hover


First question:

I am currently working with the mousetrap plugin trying to create a hover. So, only data after an invisible vertical line is being gathered. Unfortunately the mousetrap plugin virtually has the opposite function: the stopping boundaries.

The start coordinates are fixed at 0;280, meaning the cursor starts at the bottom center. In order to get a hover, I put two mousetrap elements in a row. The first one having a stopping boundary at: upper=128 lower=no left=-512 right=512. And the second one having no stopping boundary as it's meant to gather all the data once the boundary is crossed.

The problem however, is that the first mousetrap element does not stop exactly at the position of the hover (y-axis = 128), but one timestamp later. This means the data for the ordinate of the first mousetrap element tends to be something from 70 to 127. This deviation obviously is smaller if the logging resolution is set to 1 ms compared to 10 ms, still the first element goes one measurement too far.

The second element starts precisely where the first element stopped. So, if the first element stopped at y-axis= 120, the second element starts tracking the data from y-axis = 120.

My main problem with this: The starting point after the hover differs. Therefore, for most trials the starting point on the ordinate is a different one. Depending on how quickly one moves the cursor over the hover the deviation from 128 increases.

My question: Is there a way to create a hover, where the first value of the ordinate of the tracked data is always the same. So that after the vertical line at y-axis = 128, the first coordinate to be tracked is y-axis =128. Obviously the abscissa values will differ. 


If you find my wording imprecise or you struggle to understand my issue, feel free to tell me, so I can try and give a better explanation.


Second question:

As the experiment is meant to run on computer, tablet and smartphone: does anyone have any recommendations as to which device would be reasonable to buy?

I know the app was conducted for the Nexus 4 and 9 as reference devices, but it would be practical to conduct the experiment on a more up to date smartphone. Besides all the smartphones I tried so far (mainly Samsung) have problems with the OpenSesame app.


Thanks in advance!



  • Hi David,

    concerning the first question: Is this something that needs to be implemented in the experiment itself? That is, except for the fact that you want to start tracking coordinates only when y=128 are crossed, is there something that happens at this point in the experiment (e.g., a stimulus gets displayed or the like)? If not, it would probably easier to extract the relevant part of the trajectory later in the preprocessing / analysis part.

    concerning the second question: as far as I know OpenSesame does not support recent versions of Android anymore (cf. They recommend using Windows 10 tablets instead.



Sign In or Register to comment.