-
Notifications
You must be signed in to change notification settings - Fork 83
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
No text baseline alignment for combobox labels #81
Comments
The problem is in the original Darcula Look And Feel. |
The fix is also available in my fork of the Darcula Look And Feel |
@Revivius: How about including the jar of @AlexFalappa's fork instead of the original? |
@markiewb I think it is a very good idea to include @AlexFalappa's fork because original repo seems to be inactive for quite some time. Lets target this for v1.5 |
@Revivius thanks for considering my contributions. Here is the complete list of my fork improvements over the original Darcula LAF:
|
@AlexFalappa how should we proceed ? Your improvements will render some classes in ui package obsolete. Is it possible for you to create a pull request containing the JAR built from your fork and removing unrequired classes in ui package ? |
@Revivius sure, I will try to cook up something this evening. |
Done as PR #86 |
I see that the PR has diverged from master, would you like me to rebase? |
@AlexFalappa; yes please. I want to check and merge this PR as soon as possible. I am sorry for the delay. |
Made a better PR #89. |
Will close my previous PR |
@Revivius you should be able to merge cleanly now |
@AlexFalappa; merged, thank you for combobox baseline fix. Next time we should consider updating the version of the jar in lib folder. Files in lib folder (which we declare as a repo in pom) seems to be copied to local maven repo (under user home) during build. Since there already was a com.bulenkov.darcula-1.0.0.jar in my local repo I had hard time understanding why your fixes was not working. Deleting the jar from my local maven repo (again under user home) caused the updated jar (in lib folder from your PR) to be copied to there and until that point I could see modifications to jar within NetBeans and also build started to use new jar so I could see your fixes. |
@Revivius good to know that. |
The problem mainly shows in the options dialog, for exemple here:
And here:
The text was updated successfully, but these errors were encountered: