Bug 119182 - [WorkingSets] Improve Working Set selection dialog
Summary: [WorkingSets] Improve Working Set selection dialog
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-04 07:45 EST by Martin Aeschlimann CLA
Modified: 2019-09-06 15:37 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2005-12-04 07:45:18 EST
20050104

I would suggest the following improvements to the UI of the working set selection dialog:

- When 'Selected Working Sets' is not selected all controls below it should disabled as they do not apply
- The controls below the 'Selected Working Sets' radio button should get an indent to align with the text of the radio button.
- The radio button texts should use sentence capitalization, e.g. 'Selected working sets'
- There's a mix of 'working set' and 'working sets'
- Missing mnemonics
Comment 1 Kim Horne CLA 2005-12-05 11:05:23 EST
I'll fix all but the first one.  This behavior is intentional  - when you check on a box there the radio gets implicitly changed to the third option.  This means one less click for the user.  We use this idea elsewhere in the UI as well.
Comment 2 Kim Horne CLA 2006-02-13 08:26:13 EST
Punting.
Comment 3 Markus Keller CLA 2006-03-24 08:59:50 EST
I agree with Martin that the list of working sets should be disabled unless "Selected Working Sets" (misses a terminating ":") is selected. I'm not aware of other places in the UI where logically disabled controls are enabled visually.

Saving a single click or mnemonic shotcut is IMO not a good reason for showing inconsistent UI.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:37:29 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.