Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 249866

Summary:	leaving checkbox at front of Table/Tree causes invalid cases in custom draw events
Product:	[Eclipse Project] Platform	Reporter:	Grant Gayed <grant_gayed>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	cocoakevin, skovatch
Version:	3.5	Keywords:	triaged
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:	stalebug

Description Grant Gayed

2008-10-06 16:06:14 EDT

- happens on Cocoa and Carbon
- in the text below, "cocoa" == "cocoa and carbon", and "Tables" == "Tables and Trees"

On platforms != cocoa, Tables with SWT.CHECK associate the checkboxes "column" with logical column 0.  As a result, if column 0 is moved to a new position in the Table, the checkboxes move with it.

But on cocoa the checkboxes column currently always stays at left-most position in the Table.  This creates a strange situation for EraseItem/PaintItem events, because the bounds in these events should include the checkbox when sent for logical column 0.  But if logical column 0 is moved to the middle of the Table then doing this would create a bounds rectangle that spanned other columns.

Tables on cocoa currently handle this case by not extending the EraseItem/PaintItem bounds to include the checkbox if logical column 0 does not immediately follow the checkboxes.  The only way to make this case always work properly would be for the checkbox column to follow logical column 0 when it's moved.

Comment 1 Lakshmi P Shanmugam

2017-07-04 07:42:36 EDT

Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more
information.

Comment 2 Eclipse Genie

2019-12-16 14:58:55 EST

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.

--
The automated Eclipse Genie.