# Crosshair vs Slice Intersections

**URL:** <https://discourse.slicer.org/t/crosshair-vs-slice-intersections/21700>\
**Category:** Support\
**Tags:** crosshair\
**Created:** [January 29, 2022, 9:16pm UTC](https://discourse.slicer.org/t/crosshair-vs-slice-intersections/21700 "2022-01-29T21:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [January 31, 2022, 10:12pm UTC](https://discourse.slicer.org/t/crosshair-vs-slice-intersections/21700/6 "2022-01-31T22:12:10Z")

</div>

I do think these are two distinct concepts:

- crosshair is a single point in space

- slice intersections show where other slices are located on a slice view

There’s no reason to assume that the slices intersect or are orthogonal. Or that there are only two other slices to display in a given slice view. It can be useful to show the current crosshair even when it doesn’t crosshair even when it doesn’t reflect the current slice location. E.g. use shift-mousemove to position the slices and crosshair pick a reference point in 3D. Then use the slider to scroll the slices and crosshair stays at reference point and doesn’t follow, which can be handy.

---

_[View the full topic](https://discourse.slicer.org/t/crosshair-vs-slice-intersections/21700)._