CHANGE build-and-run.sh to reuse Simulator instance#7
CHANGE build-and-run.sh to reuse Simulator instance#7ninovanhooff wants to merge 4 commits intofinnvoor:mainfrom
Conversation
For enhanced developer UX
|
|
|
ah sorry I forget there already is a vscode task that calls build and run. I think we can just update that to use an alternate script, or inline this change into the task |
1d3f82d to
a98cce6
Compare
|
@finnvoor ok, I made that explicit by renaming the file and creating a new one for vscode. With this change, we indeed lose seeing the logs in the terminal, but I don't consider that a loss. The developer can open the Console window from within the running Simulator and position it as they like. This persists multiple runs since the simulator is not restarted. Restarting the simulator takes significant time, perhaps more than 2 seconds. Also, by using open, the Simulator will be launched in a separate process, which allows the build task to end. Vscode expects this. When you use the "Relaunch last task" command, vscode asks for confirmation to kill any running tasks before restarting the task, which is another hurdle for quick iteration |
problem
On MacOS, using vs code, my issue was that the simulator was completely hidden by the VS code window when running the task
Playdate: run (debug)solution
opencommand, the Simulator window receives focus