[Development] Qt5, Widget move events, and the bug that won't die

[Alex Montgomery]

Hello,

I understand that Widgets are considered "complete" in Qt5, and no new
features are going to be added, but it's seeming more and more like the
actual position of developers is that Widgets are fully deprecated.

For at least five months Digia and others have known that one of the
fundamental Widget events, QMoveEvent, has been broken in Qt5. This is
confirmed on all major platforms, and has been reported as a "known issue"
for several releases, but is getting no love from developers. Here's the
bug:
https://bugreports.qt-project.org/browse/QTBUG-32590

The only reason I can see for this bug to languish as long as it has is
that there is some disagreement over which of the duplicate move events is
the "correct" one; either the first one that agrees with QWidget::pos (as
it worked in Qt4) or the second one that seems to agree with the
documentation.

I would really appreciate it if people could weigh-in on which move event
we should cull (I think we can all agree that at least one of them is
wrong!) and maybe we can make progress on this bug. It's hard to convince
anyone to upgrade to Qt5 when it breaks core features of Qt4. I love the
direction of Qt5, but we all know that there are a lot of Widgets-based
projects in existence, and it's embarrassing that Qt5 is ignoring such a
fundamental bug in that API.

Regards,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140113/bd477f4e/attachment.html>