Community
Participate
Working Groups
SWT needs to expose some way to compute the height of a control given its width (and visa versa). Control.computeSize does not behave as documented. It takes the inner content size (the size of the control minus trim) as hints, not the actual control size. SWT does not provide API to compute the trim size of a control given its outer dimensions, and layouts only have knowledge of the outer dimensions of child controls. This enhancement asks for one of the following: 1. Change the implementation of computeSize to match its JavaDoc and the way it is being used in Eclipse. 2. Provide a new method whose behavior matches the JavaDoc for computeSize. 3. Provide a new method that returns a control's trim given its outer dimensions. Personally, I would prefer option 1. This would simplify code within SWT, and would fix downstream bugs in apps that expect computeSize to behave as documented. Options 2 or 3 would require updating the JavaDoc for computeSize to describe the actual behavior of computeSize. This is required in order for ANY layout to correctly handle wrapping text. See bug 45874 for more details
*** Bug 45874 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 9866 ***
Reopening. Bug 9866 was closed without solving this issue.
It was bogusly marked as a dup. That's why it was closed.
*** Bug 90232 has been marked as a duplicate of this bug. ***
See bug 46112, bug 104234, and bug 103863. These are the three biggest issues that are complicating the workbench layouts.
This is still a problem.
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.