News for hackers. Stuff that matters.
Re:PyQt5 Tutorial: Create a Python GUI in 2018 by toyg on Tuesday September 25, 2018 @03:49PM (#18069880)
> ui for connecting signals and slots and configuring stuff as well, but few people use it.

I try hard to do that (it saves on boilerplate), but the challenge is always in finding signals and slots with the same precise amount of parameters. Say I trigger a signal with no parameters and I want to connect it to a slot that takes a boolean always with the same value (e.g. a pressed() connected to a setEnabled(bool), where bool should always be True), I can't do that in Designer, it has to be in actual code - a trivial one-liner, sure, but still one more line of technical debt.

(INB4 "ur doing it wrong": yes, I know about clicked(bool), toggled(bool) etc, it was just an example to explain the concept.)

Re:PyQt5 Tutorial: Create a Python GUI in 2018 by ajuc on Tuesday September 25, 2018 @04:11PM (#18070069)
I don't consider connecting signals in xml (via designer) better than connecting them in code. The line is still there, just in different place.
Re:PyQt5 Tutorial: Create a Python GUI in 2018 by toyg on Tuesday September 25, 2018 @05:34PM (#18070690)
But the UI changes very rarely, and it’s out of the way most of the time; whereas the class method is always in the way in parts of code that could see a lot of day-to-day activity, migrations (py3...) and so on.
Re:PyQt5 Tutorial: Create a Python GUI in 2018 by ajuc on Tuesday September 25, 2018 @05:48PM (#18070798)
On the other hand refactoring is much easier if all your signals are connected in code.