Bug 549901 - [Win32] Table column 0 has wrong alignment
Summary: [Win32] Table column 0 has wrong alignment
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.12   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-08 16:29 EDT by Paul Pazderski CLA
Modified: 2021-07-29 09:35 EDT (History)
0 users

See Also:


Attachments
Tree Item background after resize (8.29 KB, image/png)
2019-08-08 16:29 EDT, Paul Pazderski CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Pazderski CLA 2019-08-08 16:29:10 EDT
Created attachment 279526 [details]
Tree Item background after resize

Similar to bug 549889 column 0 alignment for Table and Tree has some strange behavior.
Snippet from bug 549889 to test: https://bugs.eclipse.org/bugs/attachment.cgi?id=278304

Observations (some are bugs, some may be intentional):
 - header column 0 alignment cannot be changed with setAlignment (imo a bug)
 - Table column 0 items ignore alignment and is always left aligned (imo a bug)
 - for Tree column 0 ignores alignment and is always left aligned (probably intentional but not so nice if there is no tree/child elements)
 - after first resize of any column the background of Tree item 0 column 0 is wrong (see screenshot)
Comment 1 Eclipse Genie CLA 2021-07-29 09:35:03 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.