… as suggested by qt/README:
*dialog.(h/cpp) Various dialogs, e.g. to open a URL. Inherit from QDialog.
This seems to me to be renaming for the sake of renaming :smile: It’s possible to defend shorter naming (in the absence of ambiguity) as well.
Doesn’t seem worth keeping a tracking issue open for. I’m not sure why you open this as issue instead of a PR.
This seems to me to be renaming for the sake of renaming :smile:
Not at all ;)
Objects of QDialog
class and its subclasses could spin an additional event loop, that could block the main (GUI) event loop (#17145).
Following the naming convention, mentioned in OP, makes reasoning about possible the GUI event loop blockers easier.
I’m not sure why you open this as issue instead of a PR.
That was a deep night - just have fixed an idea before sleeping ;)