Bug 5370 - Code complete is TOO complete
Summary: Code complete is TOO complete
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Claude Knaus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 7062 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-30 17:34 EST by Jared Burns CLA
Modified: 2002-02-06 10:03 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 Jared Burns CLA 2001-10-30 17:34:15 EST 
Code complete includes fields and methods that are not code legal in the current
context. For example, code completion shows private methods defined in Object.
This not only clutters the code complete dialog with tons of useless data, it
also generates compiler errors if a user unwittingly selects a private/protected
field/method out of context.

The results of code complete should be filtered by protection and context.
Comment 1 Philipe Mulet CLA 2001-10-31 06:29:21 EST 
CodeAssist has an option to hide non-visible member completions.
JUI should expose it.

Moving to JUI
Comment 2 Erich Gamma CLA 2001-10-31 06:36:58 EST 
For now set the option to hide invisible members to off.

Once we do a code assist preference this should become a user visible option.
Comment 3 Erich Gamma CLA 2002-01-18 06:17:17 EST 
There is now a preference for controlling visibility, the option should be off
by default
Comment 4 Claude Knaus CLA 2002-01-21 06:18:38 EST 
fixed > 20020120
Comment 5 Claude Knaus CLA 2002-02-06 10:03:52 EST 
*** Bug 7062 has been marked as a duplicate of this bug. ***