I had a small task today in Marave. The goal was:
Fade in a widget
Set a variable
Fade in another one
It's important that things are done in that order and it's also important that the app remains interactive.
And here's the code to do that (simplified):
def fadein(thing, target=1., thendo=None):
* thing is a QWidget
* thing.proxy is a QGraphicsWidget
* thendo is callable
* target is the desired opacity
And this is how you use it:
Isn't that lovely? Having functions as first class objects means I can just take
later as a closure, along with
avar, which need only be defined in the local scope, and the call chain will work just as I wanted!
I think this kind of usage shows the real added value PyQt brings to the table, it's not just that python avoids the boring compiles, or that you have the awesome standard library to use, but that the language itself enables you to do things that are not practical in C++.
In C++ the only way I can think of is creating a slot that's the equivalent of later, then chaining the signals... which means that this throwaway
later becomes part of the interface of a class!
I would have to define
later somewhere else on the file, separate from its only usage (maybe even inlined in the header file).
Even then, that's not equivalent: avalue may be something that was only avalable before the first call to fadein, (for example, the time of the first fadein): I would have to create a place to store it, make it reachable by
later... and wht happens if you try to do this again while the first fadein is in progress?... it gets hairy.
Programming is like a slap in the face sometimes... you realize that things you use without even noticing are far from trivial.
So, remember young padawan: you can choose you tools. Choose wisely.