Kraut.World/server
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fixing setTimeout being called several times

Browse source
This commit is contained in:
David Négrier 2020-06-11 11:34:22 +02:00
parent ac2e45c60e
commit e50a4fd88b
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
front/src/Phaser/Game/GameManager.ts
View file

@ -185,12 +185,16 @@ export class GameManager {
this.currentGameScene = null;
}
private timeoutCallback: NodeJS.Timeout|null = null;
reconnectToGameScene(lastPositionShared: PointInterface) {
if (this.reconnectScene === null && this.currentGameScene) {
if (this.reconnectScene === null && this.currentGameScene && this.timeoutCallback === null) {
// In case we are asked to reconnect even if switchToDisconnectedScene was not triggered (can happen when a laptop goes to sleep)
this.switchToDisconnectedScene();
// Wait a bit for scene to load. Otherwise, starting ReconnectingSceneName and then starting GameScene one after the other fails for some reason.
setTimeout(() => this.reconnectToGameScene(lastPositionShared), 500);
this.timeoutCallback = setTimeout(() => {
this.reconnectToGameScene(lastPositionShared);
this.timeoutCallback = null;
}, 500);
return;
}
const game : Phaser.Scene = GameScene.createFromUrl(this.oldMapUrlFile, this.oldInstance);