Community
Participate
Working Groups
In the current implementation of TableLayout and AbstractColumnLayout the consumer can add ColumnLayoutData instances but they cannot then be retrieved from the layout. We have an uninteresting use case that I won't go into here that we need access to this data. I didn't see any reason why this was not exposed other than there wasn't a need. I'll attach a patch for TableLayout.
You should take a look at the successors of TableLayout in bug #171824. Although it doesn't provide the information either it's much better because it supports resizing.
(In reply to comment #1) > You should take a look at the successors of TableLayout in bug #171824. > Although it doesn't provide the information either it's much better because it > supports resizing. > I have and it's why I referenced AbstractColumnLayout as well in the description. We want it to only resize once so Abstract/TableColumnLayout doesn't fix out issue. But if possible it would be nice to have AbstractColumnLayout return this information as well as the patch I looked at this morning didn't provide this information either.
My vision for this was to attach this information to the Table/TreeColumn instead of adding it to the Layout, this way it would be accessible all over see bug #171844 but I'm out of time for M6. I have just a few minutes ago updated the patch in #171824 make sure you patch is against it.
(In reply to comment #3) > I have just a few minutes ago > updated the patch in #171824 make sure you patch is against it. > Will do. Thanks.
Created attachment 60742 [details] TableLayout patch
Updating the summary to just be for TableLayout.
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.