You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently MapViewState has a constructor overload taking a saved game name, which it stores locally, and then completes the load later during initialize. We should instead use single stage initialization, where the full load is done by the time the constructor completes, and if there was any error loading, it should throw from the constructor, preventing object instantiation. This prevents creating zombie objects which exist, and can have methods called, but don't really work because they're in some kind of failed state.
Currently
MapViewState
has a constructor overload taking a saved game name, which it stores locally, and then completes the load later duringinitialize
. We should instead use single stage initialization, where the full load is done by the time the constructor completes, and if there was any error loading, it shouldthrow
from the constructor, preventing object instantiation. This prevents creating zombie objects which exist, and can have methods called, but don't really work because they're in some kind of failed state.Related:
StructureManager
away from being a global #1647StructureCatalogue
fromstatic
class to regular class #1336ProductCatalogue
fromstatic
class to regular class #1337The text was updated successfully, but these errors were encountered: