Tudor sent me some files and we got it worked out. I’ve also opened an issue on github, since I assume key presses bleeding from the previous stimulus is not desired behavior. Is that right @jeremygray ? Here’s some of what I wrote in the issue ticket:
The workaround is to call event.clearEvents() before
displaying the rating scale. When the rating scale is in its own
routine, in a code component, in Begin routine, the call:
event.clearEvents()
solves the problem. When the prior Stimulus is in the same routine as
the rating scale (i.e. Show text for 3 seconds, then rating scale), the
code component has:
Begin routine
eventsCleared = False
Each frame
# assumes the rating scale is named ratingScale
if ratingScale.status == STARTED:
if not eventsCleared:
event.clearEvents()
eventsCleared = True
It was also important that the code component in the builder be positioned lower than the rating scale component, since this affects how the builder components are converted into code.