Millisecond Forums

Thanks for the data file. This confirms my suspicion that something's throwing off the mouse coordinates for some reason. You'll notice that 0-719 (720px) is only half of your actual vertical display resolution (0-1419; 1440px). The script thus doesn't "realize" that the image has been fully extended, because the relevant coordinate (1419) is never reached. Please try the following and let me know if that changes anything: Add

/ canvasposition = (50%, 50%)

to your script's <defaults> element and re-run in via the web (keep logging the mouse coordinates).

Hi Dave,

Thanks for this.  Sorry for the late reply but I have been unwell.

I have tried this and it seems to make it worse.  Whereas before it would occasionally allow the image to disappear when pulled (resulting in 719  for mouse_y), the image now must be pushed to disappear - when you pull the image it just stays on the screen (and I believe it is not allowing me to pull it as far as when there was no canvasposition included).  I have not included the data file as all the values.mouse_y were 0.

Any other thoughts?

Kind regards,

Rebecca

No, unfortunately I don't have any additional idea at the moment. It's clear that *something* is messing up the mouse coordinates (resulting in the apparent[1] freezing in "pull" trials ). What that something is, I have no clue.

> (and I believe it is not allowing me to pull it as far as when there was no canvasposition included)

The above suggests a wrongly sized and/or positioned canvas, so playing around with the scripts /canvasposition, /canvassize and /canvasaspectratio settings might help to narrow things down.

[1] It isn't actually freezing, the problem is that the mouse coordinate that would lead to the termination of the trial is never reached.