# Script to load specific modules

**URL:** <https://discourse.slicer.org/t/script-to-load-specific-modules/8224>\
**Category:** Development\
**Created:** [August 29, 2019, 1:55pm UTC](https://discourse.slicer.org/t/script-to-load-specific-modules/8224 "2019-08-29T13:55:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [August 29, 2019, 3:08pm UTC](https://discourse.slicer.org/t/script-to-load-specific-modules/8224/2 "2019-08-29T15:08:25Z")

</div>

This, perhaps?

> [@Slicer 4.11 Slice view widget interactions, intersections issue in slicelet](https://discourse.slicer.org/t/slicer-4-11-slice-view-widget-interactions-intersections-issue-in-slicelet/7383/2):
>
> Slicer has evolved a lot since the concepts of no-main-window-slicelets. Initialization of the main window has become more complicated (due to hi-DPI screens, OpenGL context initialization overrides, interaction widgets, etc.) and it is expected to get even more complex in the future (with multi-monitor support, multi-touch, pen, and Mac trackpad support, etc.). It should be still possible to mimic initialization steps of the Slicer main window in a generic widget in a Python script, but it woul…

---

_[View the full topic](https://discourse.slicer.org/t/script-to-load-specific-modules/8224)._