Community
Participate
Working Groups
Build Identifier: 20100218-1602 AbstractColumnLayout sizes the Composite's child using setSize() instead of using setBounds(). This only changes the child's size, leaving the position at (0, 0). This works when the Composite's client area includes the entire Composite, but not if the Composite has any trim. This might not technically be a bug, since the intended case of a plain Composite with a single child does work as intended, but it would be nice if an AbstractColumnLayout could also be used with a custom composite with some trim. For example, I'm currently working around a border rendering issue with UI Forms. If I use a Composite without any trim, the PaintListener installed by FormToolkit.paintBordersFor() does nothing, and I get no borders in the Windows Classic theme. If I setData(KEY_DRAW_BORDER, TREE_BORDER) on the Composite, I get an extra-wide bottom border in the Windows XP theme. If I add trim, the border renders correctly in all situations (but I currently have to override layout() to set the bounds after AbstractColumnLayout to make this work). Reproducible: Always Steps to Reproduce: 1. Create a Composite with a client area offset from (0, 0). 2. Use the Composite with an AbstractColumnLayout (like TreeColumnLayout). 3. Notice the child is located at (0, 0), rather than within the client area.
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.
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.
