Update documentation to aligh with removal of SWTResourceManager. #591
Merged
ptziegler merged 1 commit intoeclipse-windowbuilder:masterfrom Oct 22, 2023
Merged
Conversation
Contributor
Author
a5f3915 to
926ca71
Compare
Contributor
Author
|
That's quite a lot of changes... I'll try to split it up into smaller segments. |
This was referenced Oct 11, 2023
926ca71 to
0c5e52f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When the "Use ResourceManager for color/font/image access" property is set, we currently copy a static SWTResourceManager class into the user workspace. This class is then used to manage those SWT objects.
Instead, we now simply create an instance object of LocalResourceManager into the currently active class, which those calls are delegated to.
This is part of the slow removal of the SWTResourceManager.