# Resizing description field in the markups control points table

**URL:** <https://discourse.slicer.org/t/resizing-description-field-in-the-markups-control-points-table/26673>\
**Category:** Support\
**Tags:** markups\
**Created:** [December 10, 2022, 7:35am UTC](https://discourse.slicer.org/t/resizing-description-field-in-the-markups-control-points-table/26673 "2022-12-10T07:35:56Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/83011_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [December 12, 2022, 6:32pm UTC](https://discourse.slicer.org/t/resizing-description-field-in-the-markups-control-points-table/26673/21 "2022-12-12T18:32:48Z")

</div>

> [@lassoan](#):
>
> Maybe you are not concerned about the coordinates display right now, but you may need to be able to see accurate coordinate values (5-6 digits) when you work on something else in the future and then you would be bothered by the fixed RAS column widths.

True. I guess there is no auto-resize without user modifying it? (Like expand to fit the coordinates automatically).

> [@lassoan](#):
>
> Maybe moving the position status column to the left side and freeze the first few columns (selected, locked, visible, position status) would help?

Makes sense. There is no reason for them to be adjustable.

> [@lassoan](#):
>
> We need to make the control point list widget reusable (now it is hardwired into the Markups module widget) for many reasons. If we do that then the widget could be shown in the view layout (similarly to the table view) with much more space. That could also help with reducing the irresolvable size constraints.

I like that idea.

[Previous page](https://discourse.slicer.org/t/resizing-description-field-in-the-markups-control-points-table/26673.md?page=1)
