You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this has been programmed this way on purpose, but I realized that whenever I change a stimulus option in the GUI, this change is immediately implemented within a currently running stimulus. This also means that the metadata of the originally running stimulus get lost.
For my purposes, I would prefer this not to happen. For instance by not allowing the user to change settings while a stimulus is running, or only loading changed settings after the stimulus has ended.
If this is the desired behaviour of the program, it would be nice to warn users to really make sure not to change stimulus settings during a running stimulus.
The text was updated successfully, but these errors were encountered:
Agreed, it was at some point convenient to prototype stimuli and tinker with things on the fly, but is a tricky feature and can mess up experiments. Sorry if it has affected some experiments! This should change, I'll keep this open for future releases.
I don't know if this has been programmed this way on purpose, but I realized that whenever I change a stimulus option in the GUI, this change is immediately implemented within a currently running stimulus. This also means that the metadata of the originally running stimulus get lost.
For my purposes, I would prefer this not to happen. For instance by not allowing the user to change settings while a stimulus is running, or only loading changed settings after the stimulus has ended.
If this is the desired behaviour of the program, it would be nice to warn users to really make sure not to change stimulus settings during a running stimulus.
The text was updated successfully, but these errors were encountered: