| Reference | Downloads | Github

Participants screen becomes inactive when experimenter click their mouse to check Stdout in Runner

Hi there!

We have two screens computer, one screen is placed in neighboring room (where participants sit). Experiment’s design includes keyboard input. When experimenter clicks by their mouse on Runner to check Stdout field for logs, participants screen becomes inactive, so he/she aren’t able to enter an answer. Concerning this, we have to click on experiment screen each time to prevent blocking of input.
Have someone met any solutions? Thank you in advance for sharing!

It was better in last versions of PsychoPy when stdout refreshed and scrolled automatically, but now we have to click on Runner to see information about trials. This issue is not new too :frowning: Stdout updates only on mouse movement


I don’t think this is a discussion about development so I’m moving to the Builder section. There has actually been quite a bit of work on the outputs recently so hopefully this will be resolved (or maybe is already!)

Regarding the question though of the experimenter clicking on the Runner (or any other window) and trying to type this is somewhat tricky. The PTB keyboard and the ioHub keyboad classes don’t care what window is active - they both collect data from all windows but that also means that if your experimenter is typing that will also be recorded by PsychoPy as a response. On the other hand, event.getKeys only records responses when the stimulus window is active