# Reload Qt Loadable Module

**URL:** <https://discourse.slicer.org/t/reload-qt-loadable-module/11062>\
**Category:** Support\
**Created:** [April 9, 2020, 8:53pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062 "2020-04-09T20:53:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![xlucox](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/xlucox/32/6381_2.png) [@xlucox](https://discourse.slicer.org/u/xlucox)\
**Post date:** [April 9, 2020, 8:53pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/1 "2020-04-09T20:53:50Z")

</div>

Hi everyone !!!

I’m adding some functionalities to the MultiVolumeExplorer Module. I wonder if there is any easy way to reload this module from Slicer. Always when I edit the code of the module I have to restart slicer to reload this module.

Thank you very much.

Kind regards.

---

<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:** [April 9, 2020, 9:50pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/2 "2020-04-09T21:50:10Z")

</div>

No, you can’t reload the C++ based modules unfortunately.

Often it’s a good idea to put infrastructure in the C++ code, like filters or other algorithms, test it in isolation (small test programs) and then develop your module in Pythong.

---

<div class="post-metadata">

**Author:** ![xlucox](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/xlucox/32/6381_2.png) [@xlucox](https://discourse.slicer.org/u/xlucox)\
**Post date:** [April 9, 2020, 11:29pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/3 "2020-04-09T23:29:14Z")

</div>

Ok,

Thank you very much.

---

<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:** [April 10, 2020, 2:00am UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/4 "2020-04-10T02:00:03Z")

</div>

Important: Sequences will be merged into Slicer core in a couple of days (see progress [here](https://github.com/Slicer/Slicer/pull/4810)) and MultiVolume explorer will be replaced by Sequences infrastructure (which support 4D sequences of any nodes - transforms, markups, models, etc. - and not just volumes). MultiVolume modules will be probably kept around for a year or so, but no further developments will be done and at some point the modules will be moved out to an unsupported extension.

Therefore, I would not recommend to make any changes or improvements to MultiVolumeExplorer now. What improvements would you like to implement?

---

<div class="post-metadata">

**Author:** ![xlucox](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/xlucox/32/6381_2.png) [@xlucox](https://discourse.slicer.org/u/xlucox)\
**Post date:** [April 10, 2020, 4:30pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/5 "2020-04-10T16:30:22Z")

</div>

I just changed some little things.

For example: Instead of show the current frame number in the frame slider, it shows the current frame label. I also added a new button to fit the data plotted in the chart when I make a ROI.

---

<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:** [April 10, 2020, 4:44pm UTC](https://discourse.slicer.org/t/reload-qt-loadable-module/11062/6 "2020-04-10T16:44:28Z")

</div>

In Sequences you can already switch between showing index number or value (advanced section of browser).

Computing plot from a ROI is not available yet - it would be great if you could contribute it (just wait a few days until Sequences are merged into Slicer core). I would add a separate module for this (probably the current quick plotting feature will be moved out from Sequences/SequenceBrowser module to a separate module, too).