Workspace open/close patches

[bsork]

What about two new patch slots for the workspace? One to run after finished loading, and one when closing.

In my case I would for instance start a Reason file in the first, and kill it with the second. It could also be used to set defaults for the workspace like making sure the interface builder is opened or whatever.

[bsork]

...bumpety...

And I like to add that the above scenario with Reason, I now do within some "master" patch in the grid, where an "On Activation" first starts a CMD-file which kills any old Reason process that might be running, waits a couple of seconds to avoid conflicts, and then starts the relevant Reason project (if any).l

[senso]

I could be interesting to have his kind of features.
But It's probably more logical to create a initialization/finalization script associated to the workspace?

[bsork]

I think patches are the best solution, but my example wasn't really a good one. For that, some association with scripts might be better, but as we can do practically anything we want in a patch, that would be more flexible.

Other uses for startup/shutdown patches could include things like "set sequencer start to bar 4, beat 2" with the sequencer live window selected at startup, and at shutdown send some midi initialization commands (eg CC07/Volume) to some outboard equipment. Using On Activation is of course possible for startup routines as of today, but there are no options when closing the workspace but to make sure that the patch is executed before closing.