Bug 5991 - Template proposal should never be the first in the proposal list
Summary: Template proposal should never be the first in the proposal list
Status: RESOLVED DUPLICATE of bug 4978
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Claude Knaus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-16 04:50 EST by Kai-Uwe Maetzel CLA
Modified: 2001-11-16 06:32 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kai-Uwe Maetzel CLA 2001-11-16 04:50:22 EST 
Build 20011114 and earlier.

Assuming you have
  IPreferenceStore store= new PreferenceStore();
  store.s<|>

The first you see in the proposal list are the templates
 stderr, stdout, switch
which is wrong as it would produce incorrect code. In case of
switch even syntactically incorrect code. As it migth be expensive to check the 
template definition in order to find out whether a template should be proposed 
or not, templates at least should not be the first proposals in the list. In 
the majority of case I don't want a template. Currently I am forced to always 
yous the arrow keys to get the correct completion.
Comment 1 Erich Gamma CLA 2001-11-16 06:01:12 EST 
The real solution for this is to get more context information from Java Core.

We had the solution to sort the templates at the end, there was a case why we 
switched back. 

However, until we get additional smartness to switch back to the original 
behaviour.
Comment 2 Claude Knaus CLA 2001-11-16 06:32:28 EST 
reopened bug 4978

*** This bug has been marked as a duplicate of 4978 ***