On Saturday 5 October 2024 10:16:49 GMT-7 Phil Thompson via Development wrote:
> Looking at the QMetaObjectBuilder source I can't see where the QMetaType
> passed to setMetaType() is actually used. As far as I can tell the enum
> meta-types should be stored immediately after the property meta-types in
> the QMetaObject data. However if you look at the relevant part of
> qobjectmetaobjectbuilder.cpp (lines 1411 to 1441) you can see that no
> enum meta-types are stored and a nullptr (for the QMetaObject's
> meta-type) immediately follows the property meta-types. As my test case
> only has one enum I think that it's seeing that nullptr as its
> meta-type.
> 
> As QML defined enum properties are not allowed, would that mean that
> this code wouldn't have been exercised?

Correct.

QMOB is emitting current-version meta objects (as of this week, 13), which 
requires that QMetaEnums have their meta objects.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Principal Engineer - Intel DCAI Platform & System Engineering

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to