Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lazy Initialization of Map to avoid using Display Thread #198

Merged
merged 1 commit into from Aug 31, 2015

Conversation

@fgdrf
Copy link
Contributor

@fgdrf fgdrf commented Aug 27, 2015

On creation of MapImpl instances colourScheme and colorPalette are created. This causes Display thread access via PreferencesStore initialization which is problematic if using MapImpl in Test cases.

To avoid these behavior the refactoring initializes the mentioned instances lazily.

Signed-off-by: Frank Gasdorf <fgdrf@users.sourceforge.net>
fgdrf added a commit that referenced this pull request Aug 31, 2015
Lazy Initialization of Map to avoid using Display Thread
@fgdrf fgdrf merged commit 08690ab into locationtech:master Aug 31, 2015
1 check passed
1 check passed
@eclipsewebmaster
ip-validation
Details
@fgdrf fgdrf deleted the fgdrf:MapImplLazyInit branch Aug 31, 2015
@fgdrf fgdrf added this to the uDig-2.0.0 milestone Sep 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant