Community
Participate
Working Groups
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.
the problem is that, when you use parameter guessing, you still want to choose one particular method.
Perhaps the entries for an overloaded method could be aggregated into a tree node?
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.
*** Bug 441178 has been marked as a duplicate of this bug. ***