Bug 3515 - Type Selection Dialog: strange selection behaviour (1G47DCV)
Summary: Type Selection Dialog: strange selection behaviour (1G47DCV)
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Claude Knaus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:56 EDT by Martin Aeschlimann CLA
Modified: 2002-01-16 09:59 EST (History)
0 users

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 Martin Aeschlimann CLA 2001-10-10 22:56:25 EDT 
MA (11/10/00 4:07:48 PM)
a.	1. open the open type selection dialog
	2. in the upper pane select the last entry in the list
	3. the lower pane is updated, but after 1/4 second the upper list scrolls up one line. strange behaviour
	
b.	1. choose a type in the uper pane that exists in more that one package
	2. choose a the second package in the lower pane.
	3. now select the type again in the upper pane -> the selection in the lower pane goes back to first package


c.	why is the type selection dialog not resizable?

d. double click right mouse button also works to select an entry. is that normal?

NOTES:
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:15:07 EDT 
moved to 'active'
Comment 2 Martin Aeschlimann CLA 2001-10-16 12:34:56 EDT 
(b.) is  still not fixed
Comment 3 DJ Houghton CLA 2001-10-24 07:11:20 EDT 
PRODUCT VERSION:
	eclipse-vame-0.011
Comment 4 Claude Knaus CLA 2001-11-15 04:57:49 EST 
fixed in 20011115
Comment 5 Darin Swanson CLA 2001-11-15 12:15:06 EST 
Seems the fix for this has broken the update of the type qualifier.
Open the "Open Type Selection Dialog"
Type in ConsoleDocument

The lower pane is not showing the correct package.
Reselecting ConsoleDocument in the "Matching types" updates the package 
correctly.
Comment 6 Claude Knaus CLA 2001-11-16 03:57:11 EST 
Thanks. It's fixed in 20011116.