Community
Participate
Working Groups
3.3M7 I20070503-1400 Trying to Ctrl-Space (or just typing '.') after most terms pops up an intrusive dialogue reporting no default proposal kinds using 3.3M7 out-of-the-box. Including: System. // should propose members import java. // should propose packages syso<Ctrl-Space> // should expand to System.out.println() StringTokenizer<Ctrl-Space> // should import java.util.StringTokenizer
Created attachment 66024 [details] No proposals No proposals after typing "Color."
Clicking Restore Defaults works, and I've just noticed this happening in M6 as well (different workspace) which was working fine earlier so might be something to do with the way I am using Eclipse, though like I say it's pretty much a vanilla install that I am using. In both cases no options were checked in the first list on the Advanced Content Assist preferences page. I have not changed those settings myself so don't know what caused the first three items to become unchecked.
Cannot reproduce using I20070503-1400. Did you eventually install some plug-ins on-top of Eclipse SDK which you missed to re-install after the upgrade? Maybe one of those messed up the preference (e.g. old Mylar versions did so). Try whether pressing 'Restore Default's on Java > Editor > Content Assist > Advanced fixes the problems. Another cause could be a messed up build path.
>Try whether pressing 'Restore Default's Sorry, you already wrote that this worked ;-)
Can you reproduce this using just plain Eclipse SDK?
Under 3.3M6 I did install some Europa plugins including Mylar (but a recent version - installed within the past fortnight via update manager), but I disabled these after encountering bug 92250 which caused a few spontaneous crashes whilst lazy loading. M7 had no additional plugins installed. The problem seemed to affect a couple of workspaces - one open in M7 which had previously been open in M6, one new in M6. Restoring the defaults in each workspace fixes the problem. It might be that some plugin has disrupted the settings on both workspaces. On restoring the settings and switching to a fresh workspace I have not encountered the problem again (either in M6 or M7). I'll keep my eye out in case I see this or a similar issue again and can track down the cause. Happy to WORKSFORME.
Get rid of deprecated state.
.
