Community
Participate
Working Groups
Hi, I've noticed that the TableColumnLayout stops resizing the columns after one column has been resized by the user. Don't know if this is a bug or a feature ;-). To reproduce: 1. Get and run JFace Snippet #16 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.jface.snippets/Eclipse%20JFace%20Snippets/org/eclipse/jface/snippets/layout/Snippet016TableLayout.java?view=co 2. Resize the first column by hand 3. Decrease the width of the shell by hand Tested with 3.4 - eclipse-SDK-I20071101-0010-win32.zip
Well the column you resized manually keeps the size it. In the Snippet there are only 2 columns so the first one doesn't resize any more. What did you expected? If you add one more column you'd notice that it will still resize itself appropriately. So this expected behaviour although we could think about giving the user the possibility to reset the layout or we could add another ColumnLayoutData type which supports this.
Hi Tom, actually I have a different expectation :-). I expected that the columns *keep* their relative widths even after the user has resized one. Instead that column seems to be "locked in". Example: Assume two columns, both using ColumnWeightData with 50 "points" each. When the shell opens both have 50% of the width. The user resizes the first one to 20% of the width, column two has now 80%. Now the shell is made narrower so that is has only a third of the original width. I would expect the resulting width distribution between the two columns to still be 20% / 80%. Instead the result is closer to 66% / 33% (e.g. column one kept it's width of 20% of the original size; about 2/3 of the new size, while column two takes the rest (1/3)). Did I misunderstand something? Thanks, Elias.
Hitesh is now responsible for watching bugs in the [Viewers] component 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.
