Delay initialization of the UserPreferencesManager. #4005
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow the InstanceManager to initialize the default instance of the UserPreferencesManager after it has created the default instance.
Fixes #3999.
The problem here was that, in the absence of per-profile/per-computer stored user preferences, and in the presence of the older-style per-profile/all-computers stored user preferences, creating and initializing the default instance before registering it was causing the infinite looping. The solution was to implement the InstanceManagerAutoInitialize interface for JmriUserPreferencesManager and to move its initialization into the initialize method(). This allows the InstanceManager to register and create the default and then initialize it.