In the dim dark past, one could automate with batch files and the sendkeys command. However, any little glitch inside the called program and it would turn to $#!t!
Unfortunately, Cubase doesn’t expose an automation object for use by scripting or PowerShell.
hehe, generic remote. Idon’t know that GR will allow what the OP wants though. Also, I’m not sure what the process he described would gain. I pretty much use templates to initiate new projects and I open existing project directly. But, maybe his question is just an example for a different end.
Yes, the cited steps are really too trivial for automation, when a static template will do it. Perhaps there is a bigger goal in this, on which we will have to await the OP’s input for clarification.
Just to finish the thought on PowerShell, many people don’t realize that it will reference pretty much any .Net library. So, any function you could perform in an application could be scripted. That includes some of the handle capture stuff like someone did with that little hack util for fixing the “always on top” thing.
Have to use a lot of defensive programming when trying to control anything that users can be doing stuff with at the same time. Can’t rely on anything being where it was a moment before. The usage scenarios really have to justify the design and testing effort.
very true, but for repetitive setup or teardown operations it is nice. We use it to stage application servers, including performing admin console functions. But, as you say, we make a lot of “state” assumptions because we are in control.