[Development] Changed enum property behaviour in Qt v6.8
Phil Thompson
phil at riverbankcomputing.com
Thu Oct 3 17:52:56 CEST 2024
On 03/10/2024 16:31, Volker Hilsheimer wrote:
>> On 3 Oct 2024, at 17:07, Phil Thompson via Development
>> <development at qt-project.org> wrote:
>>
>> On 03/10/2024 15:44, Thiago Macieira wrote:
>>> On Thursday 3 October 2024 05:06:08 GMT-7 Phil Thompson via
>>> Development wrote:
>>>> Yes, that's the change - commenting out the new test fixes the
>>>> problem.
>>>> I am dynamically building the meta-object. You don't really build an
>>>> enum, you just provide a description of it to the meta-object. It
>>>> would
>>>> be nice to be able to register an enum with the meta-type system
>>>> dynamically.
>>> Or you can set the EnumOrFlag flag in the QMetaProperty flags field
>>> to
>>> force the
>>> constructor to search.
>>
>> Sorry, can you be more specific? I can't see how to do it given the
>> private nature of the flags.
>>
>> Phil
>
>
> Hey Phil,
>
> How do you generate a dynamic meta object without using private APIs?
> Do you use QMetaObjectBuilder (which is private), or do you generate
> the tables and arrays by hand?
>
> If you use QMetaObjectBuilder, then
> QMetaPropertyBuilder::setEnumOrFlag would be the way to go.
>
> Volker
I'm using QMetaObjectBuilder and already calling setEnumOrFlag, so that
doesn't seem to solve the problem.
An alternative that would work for me would be to bypass the new test if
the meta-type was invalid (ie. the enum wasn't registered) but I don't
know if that would nullify the purpose of the new test.
Phil
More information about the Development
mailing list