NetBeans IDE Dev (Build 070521)
1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03
Linux version 2.6.20-15-386 running on i386
en_US (nb); UTF-8
The code completion popup window displays the return value instead of the name
for the javax.lang.model.element.AnnotationMirror#getElementValues() method,
i.e. you can see only "Map<? extends ... >' in the popup, not the name.
Caused by the length of return type. There is no space left for the method name
Right, the problem seems to exist anywhere where the return type is long
enough. Rather confusing since the methods with long return types are also
incorrectly sorted (they seem to be sorted alphabetically according to their
return type, not their name). Would be nice if the popup would scale
*** Issue 112341 has been marked as a duplicate of this issue. ***
Please note the suggestion in issue 112341 to give the name and parameter list precedence over the (return) type. This
might be much easier to implement, as a first step, than scaling of the popup.
Note that horizontal scaling has been implemented some time ago.
I'm not sure how horizontal scaling is supposed to work, but I just tested this in NB 6.5 final and still get names
that are cut off in favor of the return type. See the next attached screenshot.
Created attachment 73926 [details]
Screenshot of CC popup where a name is truncated in favor of a return type. The full name would have been "getDisplayStringFn()".
can't reproduce in 090409,
made inner class like:
public static class BBB
public static Map<Map<Map<String,String>,Map<String,String>>,Map<Map<String,String>,Map<String,String>>>
and tried to call this method, first - name is shown first in completion list, and second this list is wide enough to
show return type also.
It still occurs when the CC popup is not wide enough. I'm attaching a screenshot with your example on my display
(1280×1024), with maximized NetBeans window. Note how only "..." is shown for the method name.
Created attachment 80183 [details]
Screenshot of the problem with build 200904150201.
in my opinion it's not exactly the same as initial issue, but ok, seems to be an issue in the same area.
Bug prior to 7.0, not touched for the last 2 years --> P4.
Sounds like an enh request to me.