Bug 181316 - [Viewers] Add default check/gray behavior to the CheckboxTreeViewer
Summary: [Viewers] Add default check/gray behavior to the CheckboxTreeViewer
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-05 16:46 EDT by Keith McQueen CLA
Modified: 2019-09-06 16:12 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Keith McQueen CLA 2007-04-05 16:46:21 EDT
I have used the org.eclipse.jface.viewers.CheckboxTreeViewer and generally find it to be what I needed.  However, I was disappointed to find that when I check a leaf node in the tree, that its parent(s) are not automatically grayed.  This seems to be the default behavior that everyone expects from a check tree, but it seems like the developer has to implement it every time he/she uses the CheckboxTreeViewer.  I could see that *maybe* someone *might* want the behavior to be different, but then that seems like an exceptional case where he/she could override to provide the desired functionality.  It is a pain for me to have to implement the logic to check how many of the children are checked to determine if the parent node should be checked and/or grayed when this is behavior that I expect to just be a part of the viewer.  Okay, I'm repeating myself, but you get the point.

Thanks
Comment 1 Boris Bokowski CLA 2009-11-26 09:48:40 EST
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:12:09 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.