Currently Stitch doesn't close the running game instance when you hit "play", which would match GameMaker's behavior.
This makes it easy to unintentionally run multiple instances of the game, which is typically not what people want.
Due to how Igor runs projects, we can't simply send a Ctrl+C/sigterm to the terminal used to run the project. We'll have to instead do something like look up the process by name.
adam-coster
commented
11 months ago
Currently Stitch doesn't close the running game instance when you hit "play", which would match GameMaker's behavior.
This makes it easy to unintentionally run multiple instances of the game, which is typically not what people want.
Due to how Igor runs projects, we can't simply send a Ctrl+C/sigterm to the terminal used to run the project. We'll have to instead do something like look up the process by name.
Note that the process name probably comes from:
options_windows.yy>option_windows_display_name