Update swingx from 1.6.1 to 1.6.4 #2356
Merged
Conversation
This file contains 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
koppor
added
the
status: ready-for-review
|
I tested this and, at least for me, there seems to be no flickering effect. So, I think we should go ahead. The only long-term solution will be to get rid of swingx. Hopefully, this is possible in the course of JavaFX. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The changelog of swingx is available there: https://java.net/jira/browse/SWINGX?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
The only changelog entry with "memory leak" is https://java.net/jira/browse/SWINGX-299. I don't know, wether this is related.
I am aware of #271. Thus, I manually tested which version to use and 1.6.4 seems to be the latest version usable.
We should check whether this helps solving #2247.
gradle localizationUpdate?