Eye Calibrator Window

Support
1

Hello Chris,

I’m loading a calibration program that is nearly identical to one Najib was using in 0.4.3 (in MW 0.4.3). I can see the eye signal in the Eye Window but the Eye Calibrator Window is completely blank. Any idea what might be going on? Is there some preference that needs to be set?

I’m using the standard_eye_calibrator.

Thanks,

Nicole

P.S. I’m waiting for the new graphics cards to arrive but from what I’ve been hearing, I anticipate that they will do the trick with the dual display.

2

Hi Nicole,

I’m not sure I understand what you mean by “completely blank”. I’ve attached a screen capture of the Eye Calibrator Window running on my laptop. Is this different than what you see? Are all the fields blank for you, or is there no content in the window whatsoever (no labels, text fields, or buttons)?

Thanks,
Chris

3

Attachment: eyecalwindow.jpg (17.8 KB)

4

Hi Chris,

I mean literally blank - see screen capture. The same thing happens when I load one of the example experiments (e.g. ShowStimulus.xml), making me think I’m just missing some command in the file.

Thanks,

Nicole

5

Screen shot attached.

6

Attachment: eye_calNR.jpg (13.2 KB)

7

Hey Nicole,

That’s very weird. It seems like the CalibratorWindow plugin isn’t loading properly. Maybe some of its files have been damaged somehow?

Let me see if I can get this to happen on my workstation. Are you running under OS X 10.5?

Thanks,
Chris

8

Hi Chris,

It is happening on multiple machines, both running 10.5 (with MW downloaded separately from the wiki).

Nicole

9

Hi Chris,

I also put in an inquiry with Elias to see if he might know the answer. He replied:

“A bug in MW 0.4.3 is that you have to open the Eye Calibrator Window using “Show All.” If you try to open it individually using “Eye Calibrator Window,” it will come up blank.”

I tried this and it does indeed work.

Nicole

10

Hi Nicole,

Thanks for passing on the info from Elias. I’ve verified that the Eye Calibrator Window is blank when you open it individually in 0.4.3, and I’ve also confirmed that the problem is fixed in the latest code. (However, I haven’t been able to figure out when it was fixed.)

Given that there’s a workaround for 0.4.3 and a fix in the latest (soon to be 0.4.4) code, I’m going to mark this issue resolved.

Chris