ioHub
ioHub copied to clipboard
DIsplay / Screen index logic fails sometimes
On multimonitor setups, there have been two computers where the screen id determined for each monitor by ioHub is reverse to what it should be based on native Windows calls.
So ioHub and psychopy will be told to display on screen index 0, but according to the Windows, screen index 0 is actually screen index 1 (the non primary display). Both times this was seen it was with a laptop and an external monitor.
The effect is that the psychopy window for stim presentation is on the opposite monitor to what the eye tracker uses for calibration!
Only seen on windows so far.