Bug 108913 - [Dialogs] Plugin dependencies selection gives unexpected results
Summary: [Dialogs] Plugin dependencies selection gives unexpected results
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 04:09 EDT by Andy Brook CLA
Modified: 2019-09-06 15:35 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Brook CLA 2005-09-07 04:09:00 EDT
When Ive been adding plugins as dependencies, as the list is populating (due to
the large list of plugins installed on the machine), I find the plugin I want in
the top 3 and select OK (not DOUBLE click).  What happens is that the dialog
fill completes and the first item in the list is auto-selected, consequently, my
selection is ignored.  I must have done this a dozen times before twigging what
was going on.

This selection problem seems to happen on other similar dialogs as well.

The workaround is to remember to double click!  A better solution would be for
dialog NOT to select the first one in the list at the end of loading IF a
selection has already been made.
Comment 1 Wassim Melhem CLA 2006-04-23 23:03:02 EDT
This is an old general problem with populating ElementListSelectionDialog.

Although, I have not encountered it recently, so it could have gotten fixed.

Moving to the Platform/UI bucket to resolve as appropriate.
Comment 2 Eric Moffatt CLA 2006-04-24 10:38:47 EDT
Tod, this isn't a jface dlg and you're the only person on the history chain that I know...
Comment 3 Susan McCourt CLA 2009-07-09 16:55:18 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:50 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.