| Summary: | [content assist] Javadoc drawn under dock/screen during content assist | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Channing Walton <channingwalton> | ||||
| Component: | Text | Assignee: | Platform-Text-Inbox <platform-text-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | P3 | CC: | andre_weinand, iyers, malanon, michaelvanmeekeren, susan | ||||
| Version: | 3.0 | Keywords: | helpwanted | ||||
| Target Milestone: | 3.3 M1 | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Channing Walton
Can you attach a picture. Works on XP. André, do you also see this? Created attachment 9085 [details]
Example of problem
This is an example of the javadoc popup appearing under the dock and dropping
off the bottom of the screen.
*** Bug 84735 has been marked as a duplicate of this bug. *** This is an annoying bug - any chance of a fix in 3.2M4 ? I am using 3.2M3. I can only reproduce this problem if the content assist window has been manually resized (made wider) so that there is not enough space left for the comments hover both on the left and right side of the content assist window. In this case the comments hover is placed beneath content assist, and the Dock is *not* respected. Firstly let me note that this issue is with the supplementary "JavaDoc window" displayed via content assist and the supplementary "template preview" window displayed via content assist (this comes up when you up and down arrow on the template proposals). Secondly, this happens if you are editing some thing in the lower half of the editor window; the lower you are the worse the problem. In JBuilder, the windows are automatically drawn in the upper half i.e 1) find out which half of the editor you are in or if the window will fit 2) if not flip it and draw it above/below content assist window accordingly Cheers and goodwill. (In reply to comment #5) You are right, but there are times when the method signatures are long and the content assist window needs to be wider. So most of us just leave it wide enough. But with suggestion in comment #6, this should never be a problem - each user can choose the width of their content assist window. We allow the window to be placed on the left, right or bottom but not above because it would hide the text you're currently typing. I've added code that prevents from drawing over the dock/task bar but this will not help you since the only thing this fix does is make the tool tip smaller. There are two possible fixes 1) we allow to draw on top of the content assist popup *plus* line height 2) we do another iteration when trying right, left, bottom but with a smaller size We are currently not working on this for 3.2 but will happily accept a good patch. I am primarily a JBuilder user moving to Eclipse. I had spent some time building up knowledge about plugins for JBuilder and even developed a few useful plugins. I will have to start all over again to learn about Eclipse internals to submit a patch. Current projects are also keeping us very busy. In anycase thanks for the time you guys are putting into this. Greatly appreciated. Just a note on comment #8; Displaying the supplementary window above (as opposed to below) will not make any major difference. Presently, when you are closer to the lower half of the editor, the primary "content assist" window takes up a lot of space above the line being typed any way - so the suppl window will just sit above the content assist window. Time permitting - we should go for this solution. Cheers and goodwill We will have to see on all Platforms how it looks like: maybe the easiest solution is in fact to allow the additional popup to be above the content assist popup. *** Bug 136703 has been marked as a duplicate of this bug. *** This shouldn't happen any longer as the popup placement has been fixed to better choose a good location and size for both the proposal popup and the additional info. Please reopen if you still see this in an upcoming build > 20060619. (In reply to comment #12) > This shouldn't happen any longer ... thanks Tom |