QWidget pos() not updated during resizes involving origin

Question

I am desperately failing at the supposedly simple problem to obtain the position and geometry of a Qt window on the screen. I originally stumbled upon this problem in a Python/PyQt context, but have since tracked it to Qt itself, where the QWidget::pos() property is not updated when the user resizes the window using any of the top or left edges or corners, i.e., resizes that involve the origin at the top left corner, hence the position of the window.

The following Qt/C++ program is the minimum to reproduce the problem (name as Qt_test.cc and build with qmake -project Qt_test.cc; qmake; make):

#include <QApplication>
#include <QWidget>
#include <QPushButton>
#include <QDebug>

class PrintingQWidget : public QWidget {
    Q_OBJECT
    public slots:
        void print() {
            qDebug() << pos() << width() << height();
        }
};

#include "Qt_test.moc"

int main(int argc, char *argv[])
{
    QApplication app(argc, argv);
    PrintingQWidget window;

    QPushButton btn("Print position", &window);
    window.connect(&btn, SIGNAL(clicked()), SLOT(print()));

    window.show();

   return app.exec();
}

Click on "Print position" to obtain the coordinates of the window, then resize the window using the top or left edges, and click again. On my system (MacOSX), the window position in the QWidget::pos() property was not updated. I clearly understand from the documentation that QWidget::pos() should always yield the coordinates of the top-left corner of the widget, which is not the case.

Anyone able to reproduce this problem? Any workarounds?

Answer 1

OK, it appears that this is actually a bug in Qt 4.8. My example program, as well as Merlin069's version, behave perfectly fine with Qt 5. Both Qt 4.8.2 and Qt 4.8.4 are affected by the bug. (For Qt 4.8.4, I tested both the homebrew and dmg installations, which both behave incorrectly). My test system was MacOSX 10.7.5.

Maybe some of you with different systems/Qt versions can still run the test program and report back, so that I can file a better bug report?