Bug 34467

Summary: [Working Sets] "Select Working Set" - item selected but "OK" disabled
Product: [Eclipse Project] Platform Reporter: Kevin McGuire <Kevin_McGuire>
Component: UIAssignee: Kim Horne <eclipse>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 Keywords: usability
Version: 2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Kevin McGuire CLA 2003-03-10 16:06:17 EST 
1. create a working set "Test"
2. again, pick "Select Working Set..."

Observer #1 => the working "Test" is selected in the list prompt but OK is 
disabled.

If you simply manually select (with the mouse) that already selected item, OK 
will be enabled.  Thus in Observe #1 "OK" should've been enabled since the 
list selection is the same.
Comment 1 Kevin McGuire CLA 2003-03-10 16:06:30 EST 
RC2
Comment 2 Knut Radloff CLA 2003-03-13 09:55:02 EST 
To make this work as intended ok should remain disabled unless a different item 
is selected.
The intent was to only enable ok if something has changed. Either a remove, 
edit or selection change. I'm not so sure anymore that this is actually useful 
though and we may just want to always enable ok.
In any case, not for 2.1.
Comment 3 Nick Edgar CLA 2003-03-21 16:13:55 EST 
Deferred.
Comment 4 Knut Radloff CLA 2003-09-02 17:17:59 EDT 
Reassigning to Nick since he is taking ownership of this component.
Comment 5 Chris Tilt CLA 2004-02-26 14:08:18 EST 
Nick, can I help out on this one? Is WorkingSetSelectionDialog the right place
to look? I'll also look at some of the other Workingset bugs if that's ok with you.
Cheers, Chris
Comment 6 Nick Edgar CLA 2004-02-26 16:16:24 EST 
Sure, thanks.
Comment 7 Michael Van Meekeren CLA 2004-05-25 11:55:43 EDT 
R3.0 you can also select an itme (ok enabled) then de-select (ctrl+mouseclick) 
and the ok button is still enabled.
Comment 8 Kim Horne CLA 2005-12-02 11:28:36 EST 
Marking as invalid.  A dialog with a disabled ok button is a bit of a freak IMO.  We don't have anything else like that I could find.  I've gone and made the button always available as per bug 117390.