# Second layout manager rendering issue

**URL:** https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643
**Category:** Support
**Created:** [April 29, 2019, 7:51pm UTC](https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643 "2019-04-29T19:51:23Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [April 29, 2019, 7:51pm UTC](https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643/1 "2019-04-29T19:51:23Z")

</div>

I have a second layout manager that I’m using in an outside window (Slicer main window not displayed). Does anyone recognize what this rendering issue might mean? Not setting some size policy correctly?

```python
layout_widget = slicer.qMRMLLayoutWidget()
layout_widget.setMRMLScene(slicer.mrmlScene)
layout_manager = slicer.qSlicerLayoutManager()
layout_manager.setMRMLScene(slicer.mrmlScene)
layout_widget.setLayoutManager(layout_manager)
slicer.app.setLayoutManager(layout_manager)

slicer_views_layout = self.findChild(qt.QVBoxLayout, "slicer_views_layout")
slicer_views_layout.addWidget(layout_widget)

```

 ![layout-manager-problem-1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/d/cd1c2afe5cf8292ef83f2cefa1c7608f7d7109f7.png)

---

<div class="post-metadata">

### Author: ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [April 29, 2019, 7:57pm UTC](https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643/2 "2019-04-29T19:57:15Z")

</div>

and another…

 ![layout-manager-problem-2](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/9/1/91de67cb1b163149fde734d5b33573b583c56ef6.png)

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [April 29, 2019, 8:12pm UTC](https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643/3 "2019-04-29T20:12:46Z")

</div>

I haven’t seen these artifacts before, but it may be because you set the layout manager to Slicer app. This is how a second layout manager is created in an existing slicelet:

> <https://github.com/SlicerRt/GelDosimetryAnalysis/blob/master/GelDosimetryAnalysis/GelDosimetryAnalysis.py#L159-L161>

So no layout manager is created explicitly and it is not set to the app. I think it should not be set to the app if you use a second window, because the Slicer app layout manager corresponds to the main Slicer window’s layout.  
Check out the rest of the file for usage (see `self.layoutWidget.layoutManager()`).

---

<div class="post-metadata">

### Author: ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [April 29, 2019, 9:41pm UTC](https://discourse.slicer.org/t/second-layout-manager-rendering-issue/6643/4 "2019-04-29T21:41:12Z")

</div>

@cpinter, you were correct about setting the layout manager to slicer app causing the issues. I commented out the lines as seen below and the rendering issues have appeared to go away.

```python
layout_widget = slicer.qMRMLLayoutWidget()
layout_widget.setMRMLScene(slicer.mrmlScene)
# layout_manager = slicer.qSlicerLayoutManager()
# layout_manager.setMRMLScene(slicer.mrmlScene)
# layout_widget.setLayoutManager(layout_manager)
# slicer.app.setLayoutManager(layout_manager)

slicer_views_layout = self.findChild(qt.QVBoxLayout, "slicer_views_layout")
slicer_views_layout.addWidget(layout_widget)

```