After working with the introduction to PySide6, I began to develop a simple GUI for an app. One thing I noticed is the requirement to add a component, like a QLabel, then having to determine where the Layout should lie. When I'm working with a list of things that need to be input, I end up with stuff like class MainWindow(QMainWindow): def __init__(self): super().__init__() # Many declarations of attributes self.line_name = QLabel("Name") self.input_name = QInput("Example Name") self.line_email = QLabel("Email") self.input_email = QInput("email@example.com") self.radio1 = QRadioButton("Option 1") self.radio2 = QRadioButton("Option 2") self.radio3 = QRadioButton("Option 3") ... # Many calls to "add Layout" for each attribute self.layout.addWidget(self.line_name) self.layout.addWidget(self.input_name) self.layout.addWidget(self.line_email) self.layout.addWidget(self.input_email) self.layout.addWidget(self.radio1) self.layout.addWidget(self.radio2 self.layout.addWidget(self.radio3 ... I found that I can create a helper method and use setattr to set each attribute instead, with an additional call to add the widget to the layout. This simplifies? it to where I only need to call the method to add the widget and set the layout. For example, class MainWindow(QMainWindow): def add(self, name, widget): setattr(self, name, widget) self.layout.addWidget(widget) def __init__(self): super().__init__() self.add('line_name', QLabel("Name") self.add('input_name', QInput("Example Name") self.add('line_email', QLabel("Email") self.add('input_email', QInput("email@example.com") self.add('radio1', QRadioButton("Option 1") self.add('radio2', QRadioButton("Option 2") self.add('radio3', QRadioButton("Option 3") I am looking for a more in-depth answer on why such a feature isn't a "default," or if there are problems with my solution. This is a general question asking is there a way to do this better, are there any drawbacks to my current solution? Continue reading...
