Relintai 4f9dd569b8 Now the Engine has methods to store globals (custom singletons). They are mostly meant for classes like EditorInterface, SpatialEditor, and plugin scripts that need a singleton for in-editor use. In essence it provides easy and side effect less access for classes that might not be present on every run. (For example gdscript recognizes normal singletons as keywords, but not these.)		2022-08-23 13:13:39 +02:00
..
engine.cpp	Now the Engine has methods to store globals (custom singletons). They are mostly meant for classes like EditorInterface, SpatialEditor, and plugin scripts that need a singleton for in-editor use. In essence it provides easy and side effect less access for classes that might not be present on every run. (For example gdscript recognizes normal singletons as keywords, but not these.)	2022-08-23 13:13:39 +02:00
engine.h	Now the Engine has methods to store globals (custom singletons). They are mostly meant for classes like EditorInterface, SpatialEditor, and plugin scripts that need a singleton for in-editor use. In essence it provides easy and side effect less access for classes that might not be present on every run. (For example gdscript recognizes normal singletons as keywords, but not these.)	2022-08-23 13:13:39 +02:00
project_settings.cpp	Moved Engine and projectSettings.	2022-08-17 15:35:28 +02:00
project_settings.h	Moved Engine and projectSettings.	2022-08-17 15:35:28 +02:00
SCsub	Moved Engine and projectSettings.	2022-08-17 15:35:28 +02:00