> From: Olivier Goffart
> On Thursday 09 February 2012 10:42:07 Thiago Macieira wrote:
>> On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote:
>> > Hi,
>> >
>> > Does anybody know why we have separation between QMetaTypeId and
>> >
>> > QMetaTypeId2 classes?
>>
>> Becaus
On Thursday, 9 de February de 2012 12.39.54, Stephen Kelly wrote:
> I always thought they were split so that Qt could add new built-in metatypes
> without breaking user code.
That's not why it was added.
> Eg, if you merge them, any user code doing:
>
> Q_DECLARE_METATYPE(QModelIndex)
Most types
On Thursday, 9 de February de 2012 14.11.17, André Somers wrote:
> Not hindered by any knowledge of the internals of these classes:
> Would it be possible to make such a statement a no-op then if the type
> is already registered?
If you can find a way to do that, great.
The problem is we haven't
Op 9-2-2012 12:39, Stephen Kelly schreef:
> Can I merge QMetaTypeId and QMetaTypeId2?
I always thought they were split so that Qt could add new built-in
metatypes without breaking user code.
Eg, if you merge them, any user code doing:
Q_DECLARE_METATYPE(QModelIndex)
will no longer compile
On Thursday 09 February 2012 10:42:07 Thiago Macieira wrote:
> On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote:
> > Hi,
> >
> > Does anybody know why we have separation between QMetaTypeId and
> >
> > QMetaTypeId2 classes?
>
> Because the original QMetaTypeId that existed in
On Thursday, February 09, 2012 10:07:16 Jedrzej Nowacki wrote:
> Hi,
>
> Does anybody know why we have separation between QMetaTypeId and
> QMetaTypeId2 classes?
>
> QMetaTypeId2 delegates all operations to QMetaTypeId by default and
> qMetaTypeId() function is calling QMetaTypeId2. To make i
On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote:
> Hi,
>
> Does anybody know why we have separation between QMetaTypeId and
> QMetaTypeId2 classes?
Because the original QMetaTypeId that existed in Qt 4.0 lacked one important
feature, which Harald fixed in 4.2 or 4.3.
Before h
Hi,
Does anybody know why we have separation between QMetaTypeId and
QMetaTypeId2 classes?
QMetaTypeId2 delegates all operations to QMetaTypeId by default and
qMetaTypeId() function is calling QMetaTypeId2. To make it more complex
Q_DECLARE_METATYPE is specializing QMetaTypeId but Q_DECLA
