Closed chrisrust closed 2 months ago
Thanks for your feature request! If you (or somebody else) create a proper design for this I could implement this. This includes the necessary actions (and possibly feedbacks) and data flow to be implemented as well as considerations around a confirmation action. I think that we could need both a confirmable save action and one that just overwrites the snapshot.
The underlying connection library does not support snapshot/show save at the moment. This would be the first step to implement.
I just created the necessary functions in the connection lib. It is now possible to save a snapshot by name, and we can also update the current snapshot (because we know the names of current show and snapshot).
It has to be integrated into the Companion module now.
I can see this might be tricky as the ui asks for confirmation when you save a snapshot, but being able to ensure that the current snapshot is saved when I select a new snapshot would be very helpful for my workflow, especially in soundchecks when I may be switching between acts/snapshots.
If it needs a confirmation, maybe that could be provided as a separate function, to be used on button up. In my workflow confirmation is never an issue. Losing changes is definitely an issue.