Bug 76796 - [content assist] make code completion more usable for heavily overloaded methods
Summary: [content assist] make code completion more usable for heavily overloaded methods
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0.1   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 441178 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-22 05:00 EDT by Ilja Preuss CLA
Modified: 2014-08-05 09:16 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilja Preuss CLA 2004-10-22 05:00:32 EDT
CMB wrote in the newsgroup:

"I really like the feature of
code completion but I think it should be done in the way intellisense is
done in VS. Example, now when you write System.out.p eclipse gives you a
dosen methods print(type ...) so if you'd like to do println(type ..) you
have to slide the methods killing the functionality that it's intended to
provide.
The ideal (but that's my personal oppinion, others may differ) would be
one entry for each method and then Left-Right to browse the methods
supported (in most cases you don't even care, you just insert a variable,
no? the usefull stuff is in the documentation that explains for each
method which parameter does what)."

I agree. Just try selecting an assertMethod when writing a JUnit test - the way 
it currently works, the code completion isn't that helpfull.
Comment 1 Tom Hofmann CLA 2005-05-17 12:45:49 EDT
the problem is that, when you use parameter guessing, you still want to choose
one particular method.
Comment 2 Ilja Preuss CLA 2005-05-18 03:26:44 EDT
Perhaps the entries for an overloaded method could be aggregated into a tree 
node?
Comment 3 Srgjan Srepfler CLA 2007-02-11 10:00:31 EST
Visual Studio does this elegantly by offering then entry and then switching between the methods (and documentation tooltip) with the left and right arrow keys. Once you choose your preferred signature eclipse could auto expand with a stub. I would love to see a sketch of how would a treenode look like but I don't see it more efficient then the current implementation that has it's issues with heavily overloaded methods.
Comment 4 Lukas Eder CLA 2014-08-05 09:16:58 EDT
*** Bug 441178 has been marked as a duplicate of this bug. ***