# SlicerQR Development

**URL:** <https://discourse.slicer.org/t/slicerqr-development/15954>\
**Category:** Development\
**Tags:** registration, build, segmentation, dicom, python\
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954 "2021-02-11T15:59:22Z")\
**Posts on this page:** 3\
**Page:** 9

<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:** [November 23, 2021, 10:15pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954/207 "2021-11-23T22:15:12Z")

</div>

Yes, these windows path length limitations are pretty much global. I believe @lassoan maybe said there’s a way to enable a longer path mode? I don’t use windows much.

> [@spycolyf](#):
>
> By the way, I asked my Unit Head for permission to put 3D MPR back out in Slicer open source. He is looking into it. He’s going to ask the legal folks. I’m trying to get it done before I retire in December.

That would be great - let us know if speaking to one of us could help answer any questions they have. I and others have worked with many institutions about their use of and contributions to Slicer.

---

<div class="post-metadata">

**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:** [November 24, 2021, 4:15am UTC](https://discourse.slicer.org/t/slicerqr-development/15954/208 "2021-11-24T04:15:23Z")

</div>

Paths to DICOM files can easily get extremely long when they are named automatically based on long DICOM tags (UIDs, series description, etc.).

About 1-2 years ago we implemented automatic filename generation from cryptographic hash of UIDs for filenames that are copied into Slicer’s DICOM database. Therefore, copying DICOM files into the database is very unlikely to fail due to path length limitations.

However, if the input files already have longer paths than MAX\_PATH\_LIMIT (about 260 characters), created using UNC paths or application with long path support then Slicer most likely cannot read those files. I’ve added some details about how long file support could be added to [this issue](https://github.com/Slicer/Slicer/issues/6037), but in the short term we need to keep avoiding paths longer than 260 characters on Windows.

---

<div class="post-metadata">

**Author:** ![jackyflint](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jackyflint/32/82275_2.png) [@jackyflint](https://discourse.slicer.org/u/jackyflint)\
**Post date:** [April 27, 2026, 9:56am UTC](https://discourse.slicer.org/t/slicerqr-development/15954/210 "2026-04-27T09:56:37Z")

</div>

Long Path Tool fixes errors triggered when deep folder structures exceed path limits and prevent image loading in Slicer applications.

[Previous page](https://discourse.slicer.org/t/slicerqr-development/15954.md?page=8)