Hi,
I found post #1617, which is related to my problem, very helpful but
the updated screen.dll file was not attached to it. (since it was a
year ago, I figure this is why)
My program makes use of multiple colored circles, which I have
programmed as offscreen windows to be copied during trials. Subjects
manage to get partway through the experiment (one subject even got
halfway, about 130 trials) before the computer generates the
SCREEN:FillOval Could not lock device context for drawing
error. Because I am running Windows 2000, I understand this is a bug
with PsychToolbox, and since post #1617 (which referred to DrawRect)
was also in the context of Windows 2000, I assume it is the same
problem. I was wondering if the .dll file could be re-posted, or if
there is any new information on this bug.
Also, could it be the case that this problem exists because I have
too many offscreen windows open? Due to the nature of the program,
there are more than 70 offscreen windows opened at the beginning of a
trial. We haven't had this problem pop up before, but in the other
two versions of this experiment there were a LOT fewer offscreen
windows, so I assume that with so many calls to 'FillOval' it's bound
to surface sometime. Is there some limit to how many offscreen
windows should be open at once?
Thanks!
Lyndsey
I found post #1617, which is related to my problem, very helpful but
the updated screen.dll file was not attached to it. (since it was a
year ago, I figure this is why)
My program makes use of multiple colored circles, which I have
programmed as offscreen windows to be copied during trials. Subjects
manage to get partway through the experiment (one subject even got
halfway, about 130 trials) before the computer generates the
SCREEN:FillOval Could not lock device context for drawing
error. Because I am running Windows 2000, I understand this is a bug
with PsychToolbox, and since post #1617 (which referred to DrawRect)
was also in the context of Windows 2000, I assume it is the same
problem. I was wondering if the .dll file could be re-posted, or if
there is any new information on this bug.
Also, could it be the case that this problem exists because I have
too many offscreen windows open? Due to the nature of the program,
there are more than 70 offscreen windows opened at the beginning of a
trial. We haven't had this problem pop up before, but in the other
two versions of this experiment there were a LOT fewer offscreen
windows, so I assume that with so many calls to 'FillOval' it's bound
to surface sometime. Is there some limit to how many offscreen
windows should be open at once?
Thanks!
Lyndsey