Mouse cursor remaining visible after eye tracker calibration despite definition as not visible

69 views
Skip to first unread message

Thomas Ullrich

unread,
May 26, 2015, 1:31:17 PM5/26/15
to psychop...@googlegroups.com

Hi everyone

I'm currently running experiments with an eyelink 1000+ eye tracker. I'm using Psychopy to present stimuli in combination with a pylink-based calibration routine under Windows 7 .
After initializing and minimizing the stimulus window, the calibration is shown in another window, which gets closed after calibration, followed by maximizing and activation of the stimulus window.

Although the mouse cursor is defined as invisible it remains visible (after closing the calibration window) in the middle of the stimulus window until the mouse is moved. Somehow it seems to me that the mouse cursor needs a kind of update before it gets invisible again. I would like to avoid shaking the mouse to make the mouse pointer to disappear. I tried to define the mouse pointer again as invisible, but that did not change anything. As I use pyglet for window generation, it’s not possible to simply change the position of the cursor.

Possibly it would be better to use the psychopy iohub framework for calibration and stimulus presentation. However, there is not enough time to change this before the next experiments.

Thanks in advance for any suggestions

Tom

Sol Simpson

unread,
Sep 7, 2015, 2:49:54 PM9/7/15
to psychopy-users
If using a version of psychopy that uses pyglet 1.2+, you could try changing the mouse position from within your program itself to see if it has the same effect as a manual mouse position change does in resolving the issue. You would do this by adding something like:

win =  psychopy.visual.Window(......)
# access pyglet window object used by psychopy
# and set mouse position to a new value
win
.winHandle.set_mouse_position(0,0)
win
.flip()

No idea if this will address the issue you having, just a thought.

Rachel Klein

unread,
Mar 7, 2016, 1:02:02 PM3/7/16
to psychopy-users
I was having a similar issue and your solution worked for me. Thanks!
Reply all
Reply to author
Forward
0 new messages