Bug 310796

Summary:	Need method TreeItem.showCheckBox(boolean flag)
Product:	[Eclipse Project] Platform	Reporter:	Missing name Mising name <tech.login.id2>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse.felipe, remy.suen, tech.login.id2
Version:	4.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Missing name Mising name

2010-04-28 07:25:04 EDT

If Tree is created with SWT.CHECK flag, all TreeItems display the checkbox.
This is undesirable.
Every TreeItem should have the method item.showCheckBox(boolean flag) to enable/disable the display of check-boxes.

Comment 1 Missing name Mising name

2010-05-03 06:37:45 EDT

Any ideas how long does it take for such issues to be fixed?

Comment 2 Remy Suen

2010-05-03 07:23:45 EDT

You may want to try using owner draw and draw your own checkbox instead if you're short on time.

Comment 3 Felipe Heidrich

2010-05-03 09:11:19 EDT

(In reply to comment #1)
> Any ideas how long does it take for such issues to be fixed?

1. We are passed the API freeze, no new API will be added till 3.6 ships
2. We need to determine if this feature is supported on all platforms.

Comment 4 Missing name Mising name

2010-05-13 03:16:54 EDT

Hello Remy,

Can you please elaborate your solution a little more?
"try using owner draw and draw your own checkbox"

I confess I could not get hold of it :(

Regards
Techieeee

Comment 5 Remy Suen

2010-05-13 05:51:45 EDT

(In reply to comment #4)
> Can you please elaborate your solution a little more?
> "try using owner draw and draw your own checkbox"

http://www.eclipse.org/articles/article.php?file=Article-CustomDrawingTableAndTreeItems/index.html

Or just capture your own image of a checkbox and then set it individually for TreeItems that you want to have checkboxes for.

Comment 6 Eclipse Webmaster

2019-09-06 16:16:43 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.