[Development] Qt 5.3 qmltypes update

Hartmann Thomas Thomas.Hartmann at digia.com
Mon May 5 11:08:00 CEST 2014


please note that we had to hand edit some files to work around limitations of the code model.
Currently I am aware of the fact that we have to "forward declare" Window in the qmltypes file of controls.
So please if you update a qmltypes file check the history and if you see something "weird" add Fazwi or me as a reviewer.

Kind Regards,
Thomas Hartmann
From: development-bounces+thomas.hartmann=digia.com at qt-project.org [development-bounces+thomas.hartmann=digia.com at qt-project.org] on behalf of Alan Alpert [416365416c at gmail.com]
Sent: 01 May 2014 23:28
To: development
Subject: [Development] Qt 5.3 qmltypes update

If your module has QML types, and you provide a qmltypes file, you
still need to update those manually each release.

Until we have an automated tool for this (I started work on one in
5.2, but it doesn't work anymore), a manual inspection of the qmltypes
file diffs can also help identify any QML type revisioning errors (or
accidentally exposed members). I recommend you do this if your module
has QML types.

I've done it for qtdeclarative just now (apologies for being a bit
late in the release process), it resulted in two changes; one for
qtbase and one for qtdeclarative:


Mostly just people forgetting to revision new signals, but one lucky
guy got his code into 5.3 when he clearly wasn't expecting it to make
it until 5.4 ;) . Ideally when we have an automated process for
updating qmltypes, it can do some replacement logic to pick the minor
version for new features instead of people having to guess.

Alan Alpert
Development mailing list
Development at qt-project.org

More information about the Development mailing list