Bug 553530 - TreeItem.getBounds() returns wrong width for owner-drawn trees
Summary: TreeItem.getBounds() returns wrong width for owner-drawn trees
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.14   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-27 06:24 EST by Thomas Singer CLA
Modified: 2021-11-30 14:45 EST (History)
3 users (show)

See Also:

Attachments
Snippet to reproduce (1.76 KB, text/plain)
2019-11-27 06:24 EST, Thomas Singer CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Singer CLA 2019-11-27 06:24:04 EST 
Please launch the attached snippet. Pressing Enter will log the output of item.getBounds() as well as the value of the measured size. On my Windows 10 machine the output is

bounds = Rectangle {18, 0, 2, 18}
size = Point {48, 16}

I would have expected the bounds.width to be 48, too.
Comment 1 Thomas Singer CLA 2019-11-27 06:24:43 EST 
Created attachment 280799 [details]
Snippet to reproduce
Comment 2 Andrey Loskutov CLA 2019-12-06 09:39:21 EST 
Same on Linux. Thomas, is this a regression in 4.14, or just noticed on that version?
Comment 3 Thomas Singer CLA 2019-12-06 10:47:06 EST 
I don't think it is a regression. Only detected it recently.
Comment 4 Eclipse Genie CLA 2021-11-30 12:39:34 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Comment 5 Thomas Singer CLA 2021-11-30 14:45:29 EST 
This behavior (bug?) is still reproducible.