9 commits

Author	SHA1	Message	Date
Richard Davey	1be486fab4	destroy only called once, no matter how many times the Scene restarts. Fix #3581	2018-04-17 12:25:45 +01:00
Richard Davey	07a55e5d1f	Removed debug call and merged Scene Systems boot and start sequences. Fix #3579	2018-04-17 02:34:07 +01:00
Richard Davey	ce7d67297f	Moving from 3.4.1 to 3.5.0 so we can release new camera fx and scene transitions	2018-04-15 12:44:47 +01:00
Richard Davey	205502a747	Prevent double-destroy from happening. Fix #3569 (however, Game.destroy now fails elsewhere)	2018-04-14 17:39:24 +01:00
Richard Davey	6b2307594a	Scene plugin flow overhaul ... Every Plugin has been updated to correctly follow the same flow through the Scene lifecycle. Instead of listening for the Scene 'boot' event, which is only dispatched once (when the Scene is first created), they will now listen for the Scene 'start' event, which occurs every time the Scene is started. All plugins now consistently follow the same Shutdown and Destroy patterns too, meaning they tidy-up after themselves on a shutdown, not just a destroy. Overall, this change means that there should be less issues when returning to previously closed Scenes, as the plugins will restart themselves properly.	2018-04-13 17:12:17 +01:00
Richard Davey	2813ac8162	Moved PluginManager and merged configs into single root file for easier changing.	2018-02-12 23:03:48 +00:00
Richard Davey	14c5aad929	Added jsdocs	2018-02-12 22:16:18 +00:00
Richard Davey	d1f5f8a82b	Added jsdocs	2018-02-12 16:01:21 +00:00
Richard Davey	4ec30b8db8	Recoded the Data component ... Added is back in as DataManager, which Game Objects can have an instance of. Plus exposed as DataManagerPlugin available to Scenes. Removed callback based system and implemented events and fixed the destroy method.	2018-01-30 00:55:27 +00:00