| Summary: | [content assist] "Insert best guessed arguments" doesn't work. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Alejandro Torras <atec_post> | ||||
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Alejandro Torras
I think this bug is important because it makes me erase and re-type the method arguments until I disable the "Fill method arguments and show guessed arguments" option, but doing so it just downgrades the "java edition" experience in eclipse, in my humble opinion, to a "just works" experience. Regards. This works fine for me using 3.6 M3:
0. start with new workspace
1. paste the following snippet into the Package Explorer:
public class a {
void foo() {
String stringVar;
Integer.parse
}
}
2. code assist after parse
3. select parseInt(String)
==> Integer.parseInt(stringVar)
If you still see the bug with 3.6 M3 then please reopen with more detailed steps to reproduce.
Hi Dani, Thank you for your fast reply. Following your posted test, it seems a problem with some plugin I have installed after or I just downloaded a bogus build. Should I post the "Help > About Eclipse > Installation Details > Configuration " details? Regards. Created attachment 151443 [details]
.eclipseproduct file for build-id 20090621-0832
Ops! It seems that this bug has been targeted for version 3.6 *wrongly*, because the .eclipseproduct attached shows clearly version 3.5.0 inside. Reopening the bug and changing the version to 3.5 Changing Version to 3.5 and reopening for revision. >Changing Version to 3.5 and reopening for revision. Same test case from comment 2 also works for me using Eclipse SDK R3.5 ;-) Alejandro, I suspect you have Mylyn installed and you're seeing bug 271252. Please reopen if I'm wrong. *** This bug has been marked as a duplicate of bug 271252 *** |