Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314867 - TableItem/TreeItem.getBounds() needs even more explicit documentation
Summary: TableItem/TreeItem.getBounds() needs even more explicit documentation
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-28 09:45 EDT by Markus Keller CLA
Modified: 2021-10-04 14:26 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 Markus Keller CLA 2010-05-28 09:45:41 EDT
HEAD, follow-up to bug 312315

It's unexpected that TableItem/TreeItem#getBounds() is quite different from TableItem/TreeItem#getBounds(int), since that's not the case for other #get*() and #get*(int) APIs. The Javadoc of #getBounds() should at least have an @see #getTextBounds(int).

I don't know what the method does if the Table/Tree has no columns, but if it's always the same as getTextBounds(0), that info would make the API more easily understandable.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:35:57 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.
Comment 2 Eclipse Genie CLA 2021-10-04 14:26:28 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. 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.