Scripting: Project Custom Data
Posted: Tue Oct 12, 2021 6:18 pmIn the same way you can store CustomData in markers using the API, it would be great if we could have storage in the project level as well. It could be exactly as the Project Notes, just a separate field.
This would allow an easy way of storing settings for scripts that are included in export/backup. Fusion has this ability, but of course that's per comp, not per project.
I suppose the right way to handle it would be to have custom storage on all levels:
The current workaround is to store Lua tables on disk in the temp folder but it's not ideal. You could use Project Notes if that field was accessible but then you couldn't use it for notes. Or create a special Fusion clip in the project, just for storing settings.
Having it on levels above the project would be useful too. You might want to execute a script that stores the settings made by the user, but you don't necessarily want the project to be in the unsaved state just because you have executed a script.
This would allow an easy way of storing settings for scripts that are included in export/backup. Fusion has this ability, but of course that's per comp, not per project.
I suppose the right way to handle it would be to have custom storage on all levels:
- Application
- Database
- Project
- Timeline
- Clip
- Render Queue Job
- Timeline
- Project
- Database
The current workaround is to store Lua tables on disk in the temp folder but it's not ideal. You could use Project Notes if that field was accessible but then you couldn't use it for notes. Or create a special Fusion clip in the project, just for storing settings.
Having it on levels above the project would be useful too. You might want to execute a script that stores the settings made by the user, but you don't necessarily want the project to be in the unsaved state just because you have executed a script.