Currently the gamecontroller destroys objects directly. It should not do this.
Instead, have the gamecontroller emit a signal, then have the SceneManager destroy objects. (It is not the job of the gamecontroller to move things around on the screen or eliminate them - it just makes decisions, but allows the SceneManager to take care of it)
Currently the gamecontroller destroys objects directly. It should not do this.
Instead, have the gamecontroller emit a signal, then have the SceneManager destroy objects. (It is not the job of the gamecontroller to move things around on the screen or eliminate them - it just makes decisions, but allows the SceneManager to take care of it)
Update the SceneManager to handle signals coming from the GameController requesting a game object be destroyed.
If a request comes to destroy a bullet, stash it instead by hiding it off-screen and removing it from the game loop.
Update the SceneManager to handle signals coming from the GameController requesting a game object be destroyed.
If a request comes to destroy a bullet, stash it instead by hiding it off-screen and removing it from the game loop.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the gamecontroller destroys objects directly. It should not do this.
Instead, have the gamecontroller emit a signal, then have the SceneManager destroy objects. (It is not the job of the gamecontroller to move things around on the screen or eliminate them - it just makes decisions, but allows the SceneManager to take care of it)
Update the SceneManager to handle signals coming from the GameController requesting a game object be destroyed.
If a request comes to destroy a bullet, stash it instead by hiding it off-screen and removing it from the game loop.
Done!