|author||Jędrzej Nowacki <firstname.lastname@example.org>||2012-01-30 12:21:43 +0100|
|committer||Qt by Nokia <email@example.com>||2012-02-07 08:52:32 +0100|
Align QVariant::UserType and QMetaType::User
There is no point in keeping separate values which should mean the same. QVariant::UserType was used also to construct a valid, null QVariant, containing an instance of unknown custom type. The concept was strange and useless as there was no operation that could be done on such QVariant. Therefore it was dropped. Please note that the patch slightly changes behavior of different functions accepting a type id as parameter. Before QVariant::UserType was an invalid type from QMetaType perspective (id 127 was not assigned to any built-in type), but QMetaType::User points to the first registered custom type. Change-Id: I5c7d541a9affdcdacf53a4eda2272bdafaa87b71 Reviewed-by: Kent Hansen <firstname.lastname@example.org> Reviewed-by: Lars Knoll <email@example.com> Reviewed-by: João Abecasis <firstname.lastname@example.org> Reviewed-by: Andrew Stanley-Jones <email@example.com> Reviewed-by: Aaron Kennedy <firstname.lastname@example.org>
Diffstat (limited to 'dist')
1 files changed, 7 insertions, 0 deletions
diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0
index fc5bebd11d..280b5d93f9 100644
@@ -437,6 +437,13 @@ Qt for Windows CE
cause an abort().
+ * Definition of QVariant::UserType changed. Currently it is the same as
+ QMetaType::User, which means that it points to the first registered custom
+ type, instead of a nonexistent type.
* The static function QMessageBox::question has changed the default argument