Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316012 - Inconsistency betweek column pack and double-click resize
Summary: Inconsistency betweek column pack and double-click resize
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-07 11:27 EDT by Marco Maccaferri CLA
Modified: 2019-11-14 02:17 EST (History)
1 user (show)

See Also:


Attachments
Patch (2.57 KB, patch)
2011-05-10 12:26 EDT, Marco Maccaferri CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Maccaferri CLA 2010-06-07 11:27:53 EDT
Build Identifier: M20100211-1343

There is an inconsistency between calling TableColumn.pack() and the resize when double-clicking on the column separator: with TableColumn.pack() the size of the header title is taken into account when computing the max width, while with double-click the header size is ignored, so if the cell contents is narrower than the header text the header is not completely visible.
I think that the correct behaviour is to consider the header text size in all cases.


Reproducible: Always
Comment 1 Marco Maccaferri CLA 2011-05-07 04:10:44 EDT
Any chance to get a fix for 3.7 ?
Comment 2 Marco Maccaferri CLA 2011-05-10 12:26:53 EDT
Created attachment 195240 [details]
Patch

Proposed patch attached.

I'm not sure if this is the correct way to submit a patch for SWT, anyway the fix is trivial since there is already a hook for the header divider double click, it just needs to always call column.pack.
Comment 3 Felipe Heidrich CLA 2011-05-10 13:17:17 EDT
The current behaviour is the native behaviour.
I think what is missing is Bug177175
Comment 4 Lars Vogel CLA 2019-11-14 02:17:59 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.

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.