A sensible way to address a number of other issues we've had (e.g., #252, #226) would be to add setup and teardown methods on Stim classes that do any internal validation or setup and teardown that needs to happen before transformation is applied. This could include things like opening and closing clips (for AudioStim and VideoStim classes), checking to make sure that contents of a Stim are valid (e.g., a TextStim contains text), etc. We could just trigger the setup and teardown calls from the core transformer logic, making sure that every Stim has an opportunity to do whatever it needs to.
A sensible way to address a number of other issues we've had (e.g., #252, #226) would be to add setup and teardown methods on
Stimclasses that do any internal validation or setup and teardown that needs to happen before transformation is applied. This could include things like opening and closing clips (forAudioStimandVideoStimclasses), checking to make sure that contents of aStimare valid (e.g., aTextStimcontains text), etc. We could just trigger the setup and teardown calls from the core transformer logic, making sure that everyStimhas an opportunity to do whatever it needs to.