RE: Backgroundstimuli are gone after branching

Backgroundstimuli are gone after branching

Author	Message
Rebecca17	Rebecca17 posted 5 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 7, Visits: 25	I've defined a block with 44 items. I have implemented that a latency < 1000 leads to another item ("This was to fast.") After this other item, I would like to go to the next item of the block. That does work, but all the backgroundstimuli of the block are gone now. How that?
	Reply Like 32
Dave	Dave posted 5 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	+x Rebecca17 - Wednesday, January 23, 2019 I've defined a block with 44 items. I have implemented that a latency < 1000 leads to another item ("This was to fast.") After this other item, I would like to go to the next item of the block. That does work, but all the backgroundstimuli of the block are gone now. How that? Stimuli drawn to the screen via /bgstim are drawn to the screen exactly once, at the very start of the <block>. If -- at some point during the block -- you erase the screen or overwrite those stimuli with others, those stimuli are gone. You either need to take care _not_ to erase the full screen or overwrite the background stimuli at any time during the block, or you need to forego using /bgstim and instead draw those stimuli to the screen in the same way as you do any others, i.e. via your <trial> elements' /stimulustimes or -frames. Edited 5 Years Ago by Dave
	Reply Like 30