Currently, in Stitch VSCode you can set the default config to use every time you hit F5 or otherwise run the run-project command.
For cases where the user would want to be able to frequently change between configs this is pretty inconvenient. One of the things we want to be able to do for the art pipeline is having alternate configs to boot right into different game rooms, and we should be able to do that from VSCode.
Two general approaches to this might be:
Add a few secondary commands and corresponding settings for a small number of common defaults. E.g. stitch.runProject2 (etc) with extra settings per project. This would enable the user to set up keyboard shortcuts per extra option, though it'd be tedious to implement and for the user to configure.
Add a single extra command that will first ask the user to choose the config from a quickpick menu before booting. Would require no extra setup/configuration, but could be a little tedious for the user since they'd have to make a few choices on each run.
Even if we at some point want option 1, I think that having option 2 would be generally useful and it's a lot easier to start with. So we'll do that first.
Currently, in Stitch VSCode you can set the default config to use every time you hit F5 or otherwise run the run-project command.
For cases where the user would want to be able to frequently change between configs this is pretty inconvenient. One of the things we want to be able to do for the art pipeline is having alternate configs to boot right into different game rooms, and we should be able to do that from VSCode.
Two general approaches to this might be:
stitch.runProject2
(etc) with extra settings per project. This would enable the user to set up keyboard shortcuts per extra option, though it'd be tedious to implement and for the user to configure.Even if we at some point want option 1, I think that having option 2 would be generally useful and it's a lot easier to start with. So we'll do that first.