Instead of unpacking the ui to a plain QWidget (my_widget in your case), unpack it to a subclass of QWidget that has a slot named my_slot.
Instead of unpacking the ui to a plain QWidget (my_widget in your case), unpack it to a subclass of QWidget that has a slot named my_slot.
It's nice to be important but it's more important to be nice.
The unpacking code doesn't have the subclass definition, that's the whole point, it's all going into scripting. The constraint is that the top-level class ONLY in the .ui file may be an arbitrary new class, everything which it includes must be available to the unpacker.
Essentially, the .ui is guiding the arrangement of known classes and I need to hook into the new signals and slots.
Bookmarks