Currently, clicking the "simulate" button will spawn a new simulation and add it to the "simulation" tab, automatically switching to that tab and allowing the user to switch back and forth between simulations. That's unintuitive for a few reasons:
It's possible to change the code, recompile, click over to the "simulation" tab and find a simulation still running based on old source code.
Clicking the "simulate" button will automatically restart a simulation - maybe that isn't what you wanted.
There's probably a better interface overall than having a "source" tab and a "simulation" tab.
There's also no fundamental reason why there can only be one simulation at a time - if it would make for a nice interface, we could enable the user to spawn several different simulations, perhaps to compare different points in time in the same simulation, or perhaps even relating back to different versions of the source code.
Overall, this issue serves as a place for some discussion of what the interface should look like.
Currently, clicking the "simulate" button will spawn a new simulation and add it to the "simulation" tab, automatically switching to that tab and allowing the user to switch back and forth between simulations. That's unintuitive for a few reasons:
There's probably a better interface overall than having a "source" tab and a "simulation" tab.
There's also no fundamental reason why there can only be one simulation at a time - if it would make for a nice interface, we could enable the user to spawn several different simulations, perhaps to compare different points in time in the same simulation, or perhaps even relating back to different versions of the source code.
Overall, this issue serves as a place for some discussion of what the interface should look like.