-
Notifications
You must be signed in to change notification settings - Fork 95
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
Javadoc Hover: Generic Types are hardly readable in light/default theme #1442
Comments
@RedeemerSK is that something you may work on? |
May be using bold font style will be the solution here? |
It looks like the last example the |
I would be even happy with (maybe a preference) to disable the colors like it was before ;-) |
It format the method parameter(one parameter per line) to improve readability, so I like it. |
The problem is not the method parameters! |
Thanks thats better now, but one need to focus (F2) the hover and at least under Linux its hard to oben the submenu as the hover closes in between and the Color preferences itself are empty Peek.2024-06-07.14-11.mp4 |
I have very limited expertise in Linux (distros) native graphics backends and thus I can only wonder why the hover viewer won't stay displayed after opening javadoc styling enhancements menu for you o.O. Btw, same menu (button) is available in Javadoc view.
Right now none of the type params in the content is bold. It's just that method return type section is italic which makes it to look little bit bolder. Shortly I'll post screens how it would look with type params being same font-weight like the rest of the signature - because that's the actual difference right now ... they were made lighter than the rest with the intention to decrease their contribution to visual complexity. |
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
@RedeemerSK with "normal" font weight it is better readable indeed I think one should either use colors or the lighter font weight but not both, and yes the hover/menu seems very "buggy"... |
@laeubi please what's your platform ? (linux distro / desktop environment / anything that may have something to do with how SWT renders menus). I assume you are running it natively, not in VM or some other non-native way, right ? EDIT: ignore, found the reason for buggy menu Also ... until the fix that removes lighter text makes it into future builds, for those that are impatient and also willing to walk the unlawful path and do little bit of hacking that I of course won't officially suggest (*wink* *wink*), there's a way to apply the fix to any existing eclipse installation. The fix can be manually applied to the files bundled inside org.eclipse.jdt.ui plugin JAR used by eclipse installation (present in ~/.p2/pool/plugins directory). Surprisingly for me, because since the JAR is signed, I (it seems wrongly) assumed tampering with it would render it invalid / unusable, which is not the case and eclipse has no problem starting with modified plugin JAR. |
Just noticed that hover & menu behaves differently when activated by pressing F2 (then going to menu hides the hover) compared to being activated by "entering into it" with mouse (then going to menu keeps hover displayed) on Ubuntu I'm testing this on. Will look into that. Can others confirm same behavior, @laeubi ? EDIT: found the cause (bug), fixed |
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
Also simplify populating enhancements menu & colors sub-menu by re-creating them every time they're being requested. Fixes eclipse-jdt#1442
Also simplify populating enhancements menu & colors sub-menu by re-creating them every time they're being requested. Fixes eclipse-jdt#1442
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
Also simplify populating enhancements menu & colors sub-menu by re-creating them every time they're being requested. Fixes eclipse-jdt#1442
Also simplify populating enhancements menu & colors sub-menu by re-creating them every time they're being requested. Fixes eclipse-jdt#1442
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
Re-create them every time they're being requested. Fixes eclipse-jdt#1442
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
Re-create them every time they're being requested. Fixes eclipse-jdt#1442
Fix PR: #1482. I hope it's OK I am also fixing bugged styling enhancements menu in that PR and not just the hard to read colored type parameters. If necessary, I can split into two separate PRs. |
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes eclipse-jdt#1442
Re-create them every time they're being requested. Fixes eclipse-jdt#1442
- incorrect text was searched for inside HTML content to see if enhancements are present - menu actions for enhancements enabled state were not set / left only when enhancements were present in content Fixes #1442
Re-create them every time they're being requested. Fixes #1442
the light green is hardly readable on white background (not sure why the
<?>
is printed differently) especially as a very thin font is used here. If more than one generic is involved it even becomes worse:The text was updated successfully, but these errors were encountered: