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
The goal of this new feature is to provide a way to preview what a routine may look like without having to run the experiment. This would be a rendering of any text, images, or other components in a routine.
Purpose
I think this would be a useful feature for finalizing experiment details such as image size, background, text, etc. This is something that I could see being very useful to save time. For example, instead of rerunning the experiment to see if the font or color of the text is better, you could just regenerate the render of the routine.
Is your feature request related to a problem?
The feature is to address a usability issue where users cannot immediately see how they are effecting the program. This feature would increase the usability of the program by providing a better way to see how the user is changing the experiment via previews.
Describe the solution you would like
I thought this could be similar to a tool like the live preview Visual Studio extension (https://marketplace.visualstudio.com/items?itemName=ms-vscode.live-server) for HTML previewing.
Ideally, the routine would be rendered in a window either under the routine section in the PsychoPy Builder or as an additional window on the side of PsychoPy Builder. If it could update automatically with changes to components in the routine that would be amazing, but even an update button that re-renders the preview would be useful.
Here is an image from the live preview extension as an example:
Describe alternatives that you have considered
The alternative is the current workaround of run the experiment after every change until all the routines are finalized.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi @janeBrusilovsky
Yes, agreed. We've discussed this internally in the core dev team too.
It becomes slightly complicated by the fact that PsychoPy Routines are dynamic (unlike OpenSesame and E-Prime which are more of a static "slide"). So I think we need a time control on the preview, like in a movie editor preview, and then we need to be able to handle variables that the stimuli are using, which might be coming from Code Components 😬
I'm saying it's a chunk of work, but I totally agree that it's a valuable feature! 😁
Description
The goal of this new feature is to provide a way to preview what a routine may look like without having to run the experiment. This would be a rendering of any text, images, or other components in a routine.
Purpose
I think this would be a useful feature for finalizing experiment details such as image size, background, text, etc. This is something that I could see being very useful to save time. For example, instead of rerunning the experiment to see if the font or color of the text is better, you could just regenerate the render of the routine.
Is your feature request related to a problem?
The feature is to address a usability issue where users cannot immediately see how they are effecting the program. This feature would increase the usability of the program by providing a better way to see how the user is changing the experiment via previews.
Describe the solution you would like
I thought this could be similar to a tool like the live preview Visual Studio extension (https://marketplace.visualstudio.com/items?itemName=ms-vscode.live-server) for HTML previewing.
Ideally, the routine would be rendered in a window either under the routine section in the PsychoPy Builder or as an additional window on the side of PsychoPy Builder. If it could update automatically with changes to components in the routine that would be amazing, but even an update button that re-renders the preview would be useful.
Here is an image from the live preview extension as an example:
Describe alternatives that you have considered
The alternative is the current workaround of run the experiment after every change until all the routines are finalized.
Additional context
No response
The text was updated successfully, but these errors were encountered: