# ROI movement points **URL:** \ **Category:** Feature requests\ **Tags:** markups-fiducials\ **Created:** [March 2, 2018, 1:39am UTC](https://discourse.slicer.org/t/roi-movement-points/2223 "2018-03-02T01:39:31Z")\ **Posts on this page:** 7\ **Page:** 1

**Author:** ![stevenagl12](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stevenagl12/32/3391_2.png) [@stevenagl12](https://discourse.slicer.org/u/stevenagl12)\ **Post date:** [March 2, 2018, 1:39am UTC](https://discourse.slicer.org/t/roi-movement-points/2223/1 "2018-03-02T01:39:32Z")

Is there any way that the future Slicer download could have either larger ROI control dots or at least the option for them. It is exceptionally challenging to be able to move them with the current settings when the user has poor vision. ---

**Author:** ![stevenagl12](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stevenagl12/32/3391_2.png) [@stevenagl12](https://discourse.slicer.org/u/stevenagl12)\ **Post date:** [March 2, 2018, 1:41am UTC](https://discourse.slicer.org/t/roi-movement-points/2223/2 "2018-03-02T01:41:59Z")

Potentially also an option to automatically fit an ROI to the vertical, horizontal, and depth dimensions of a segmentation. ---

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\ **Post date:** [March 2, 2018, 2:45pm UTC](https://discourse.slicer.org/t/roi-movement-points/2223/3 "2018-03-02T14:45:50Z")

The problem is not your vision, but high-resolution screens. ROI widget handle size is defined in pixels. I’ll update the code to size the handle relative to the window size. You can fit a ROI to a volume using `Crop volume` module. ---

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\ **Post date:** [March 2, 2018, 8:10pm UTC](https://discourse.slicer.org/t/roi-movement-points/2223/4 "2018-03-02T20:10:57Z")

I’ve updated the ROI widget handle sizing logic, it’ll be available in tomorrow’s build. It is now relative to the window size, independent from screen resolution. If you make the window larger then the handle gets larger, too, so it becomes even easier to hit. ---

**Author:** ![stevenagl12](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stevenagl12/32/3391_2.png) [@stevenagl12](https://discourse.slicer.org/u/stevenagl12)\ **Post date:** [March 6, 2018, 2:49am UTC](https://discourse.slicer.org/t/roi-movement-points/2223/5 "2018-03-06T02:49:43Z")

What I meant wasn’t fitting the ROI to a volume, but to the dimensions of a segmentation before it is converted to a labelmap. Like if it were possible for the system to parse the file to determine the dimensions of a segmentation then apply the distances and angles to obtain an ROI for easier volume cropping. ---

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\ **Post date:** [March 6, 2018, 3:53am UTC](https://discourse.slicer.org/t/roi-movement-points/2223/6 "2018-03-06T03:53:01Z")

> [@stevenagl12](#): > > What I meant wasn’t fitting the ROI to a volume, but to the dimensions of a segmentation before it is converted to a labelmap. If you don’t specify a reference volume for exporting to labelmap (in Advanced section, set Reference volume to None), then the labelmap will be automatically cropped to the necessary size on export. ---

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\ **Post date:** [March 21, 2023, 2:56am UTC](https://discourse.slicer.org/t/roi-movement-points/2223/7 "2023-03-21T02:56:31Z")