# Fill between slices, makes troubles!

**URL:** <https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706>\
**Category:** Support\
**Created:** [January 3, 2020, 4:15pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706 "2020-01-03T16:15:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [January 3, 2020, 5:46pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706/2 "2020-01-03T17:46:38Z")

</div>

I wonder if this is somewhat related to the previous discussion about slice increments?

> [@View displays lag if pixel-spacing is small](https://discourse.slicer.org/t/view-displays-lag-if-pixel-spacing-is-small/9087/4):
>
> @lassoan, I tried and think the lag is no much due to change in the units, but simply the slider has only 0.001 mm increments, so slices do not get changed until the units incremented more than 0.001 mm (which will take 10 slices in this scenario). We will encounter small voxel data more and more through SlicerMorph. I wonder if it possible to tie the precision of the slice views (current seems only three significant digits), to image precision of the volume being displayed?

---

_[View the full topic](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706)._