Community
Participate
Working Groups
Attached the screen shot. Also the screen shots of pdt issue 320709.
Created attachment 176122 [details] Screen shot
I don't think JDT is useing JFace-Tooltips but their own implementation.
Hi Tom, Thanks for the comment. Looks in the org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover class, the org.eclipse.jface.internal.text.html.BrowserInformationControl is imported. Not sure if this is the tool tip implementation of JDT, as I didn't really trace the code there. But the pdt uses the JFace BrowserInformationControl, so the issue is there any way.
Passing to JDT for a look...punt it back if this is a generic issue with the JFace browser implementation.
>Created an attachment (id=176122) [details] [diff] >Screen shot Looks OK on my system but it's always possible that some parts get cut off, especially when mixed font (styles) are used which makes the size computation very complicated. You can always move the mouse into the hover to enrich it which allows to resize it or scroll. Markus, I suggest to close as WONTFIX. >But the pdt uses the JFace BrowserInformationControl, I hope you noticed the *internal* in the name which means it can change anytime.
The size calculation is wrong right after you've changed the dialog font, but this problem is fixed when you close and reopen the open editors (we have no plans to work on that). The Browser widget does not allow us to calculate the required size (bug 232501), so we have to calculate the size manually, which is based on non-perfect heuristics (bug 232501). But the attached screenshot is strange, since the Javadoc of CoreException renders correctly for me in various fonts. Which dialog font did you use to produce this?
(In reply to comment #6) > Which dialog font did you use to produce this? Might be Trebuchet MS, just a guess though.
>Might be Trebuchet MS, just a guess though. Still works for me. Please reopen if you can provide an example including full font information.
(In reply to comment #8) > Still works for me. Please reopen if you can provide an example including full > font information. I'm not the reporter. Qiang, which font were you using?
I think the font is the default dialog font. I traced the code and it looks the font name is "Segoe UI". But the weird thing is that the dialog looks all right in a run-time environment. I.e. if I run a new time workspace against current eclipse development host environment, the tool tip looks like the screen shot 1. But the tool tips have different see also information. The Screen shot (truncated one) has the see also "IStatus", but the screen shot1(good one) has the see as "IStatus,Serialized Form". Hope this is helpful.
Created attachment 177059 [details] Screen shot1
Sorry, but we need detailed steps. I just tried again using different sizes of "Segoe UI" and it works fine. So, please only reopen if you can provide the steps.
(In reply to comment #10) > But the tool tips have different see also information. The Screen shot > (truncated one) has the see also "IStatus", but the screen shot1(good one) has > the see as "IStatus,Serialized Form". That's because in comment 1 the source of CoreException was available, but in comment 11, the Javadoc has been extracted from the attached Javadoc.
