On sexta-feira, 26 de julho de 2013 20:20:57, Alexander Syvak wrote: > About the last statement. If an object uses internally slots and signals, > it should inherit QObject.
Correct. > QObject is not copyconstructible, thus, the descendant as well. Correct. > If the object requires queued signals or QObject::property() API then > qRegisterMetaType() should be called, which > requires CopyConstructible property of the object. It's a cycle here. No, it isn't. > Where is a misunderstanding? You're confusing the the object that contains properties (that derives from QObject and is not copyable) with the type of the property. The type of properties are what we call "value-type": they are default- contructible, publicly destroyable, copyable, movable and often implicitly shared. For those reasons, they don't derive from QObject. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
