Community
Participate
Working Groups
I20080207-1530 TableColumnLayout is jumpy on the Mac. When I drag a column splitter, it only live-updates the column to the left of the splitter. The columns to the right are only resized when I release the mouse. Steps: - Preferences > General > Text Editors > Hyperlinking - click Cancel and then reopen the Preferences dialog to make sure you get the default width - drag the splitter at the right side of the "Link Kind" column to the left or to the right => when you release the mouse, the last column jumps around Interestingly, the last column stops jumping as soon as it has been manually resized once.
hm we can only readjust the size of all columns when the resizing is done and not in the meanwhile. A strange thing I'm experiencing with this table is that the scrollbar is always shown. We fixed one bug in AbstractColumnLayout in M5 need to see if this also happend before.
The current strategy is also strange on WinXP. When I open the Hyperlinking preferences page and then drag the splitter at the right of column "Modifier Keys" towards left, this actually resizes the middle column from both sides. This feels very strange, also because the grabbed splitter only moves half the distance of the mouse. As soon as I've also moved the splitter at the left of "Modifier Keys" a bit, this behavior disappears.
Does this also happen with the very small example Snippet from http://wiki.eclipse.org/JFaceSnippets#Snippet016TableLayout. Else can you modify the snippet to show the problem. It would make tracking down the problem more easily.
Yes, Snippet016TableLayout shows the problem as well if you drag the splitter at the right of "Column 2". If you add a third column, the problem is exactly the same as in the Hyperlinking preference page.
The "jumpy" bit is an SWT problem on the Mac (bug 218499). Changing summary to reflect only the problem described in comment 2 and comment 4.
multi change because of intenion of stepping back as platform-ui committer
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.
