# Understanding UI Editing and Python File Generation in 3DSlicer with Qt Designer

**URL:** https://discourse.slicer.org/t/understanding-ui-editing-and-python-file-generation-in-3dslicer-with-qt-designer/40369
**Category:** Development
**Created:** [November 25, 2024, 4:45pm UTC](https://discourse.slicer.org/t/understanding-ui-editing-and-python-file-generation-in-3dslicer-with-qt-designer/40369 "2024-11-25T16:45:32Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![shahrokh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/shahrokh/32/1499_2.png) [@shahrokh](https://discourse.slicer.org/u/shahrokh)
#### Post date: [November 27, 2024, 8:23am UTC](https://discourse.slicer.org/t/understanding-ui-editing-and-python-file-generation-in-3dslicer-with-qt-designer/40369/5 "2024-11-27T08:23:32Z")

</div>

Thank you very much for the guidance you provided. I will definitely implement the point you mentioned in my module.

The plans I have in mind are to implement modules with names such as VolumeSelector, ModelSelector, BeamSelector, etc., separately, in order to expand my experience in module development.

However, if you pay attention to the following figure, you will notice that the parent class used is of type **qMRMLWidget**. Interestingly, the **qMRMLSegmentSelectorWidget** widget does not have the **nodeType** property.

 ![1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/7/9/79341869bfc1442f52602dbb904bca27fa07b245.png)

But as mentioned you, if a widget of type **qMRMLNodeComboBox** is selected, it does have the **nodeType** property, and I think I should set it to **vtkMRMLScalarVolumeNode** or **vtkMRMLSegmentationNode** in python code.

 ![2](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/3/43251733a8241963b01c9fda03cdd9b40ed582b3.png)

Best regards.  
Shahrokh

---

_[View the full topic](https://discourse.slicer.org/t/understanding-ui-editing-and-python-file-generation-in-3dslicer-with-qt-designer/40369)._