[Interest] Need argumentative help..... giving qobject copy/assignment constructor and put it in qlist/qmap

Thiago Macieira thiago.macieira at intel.com
Thu Jul 23 08:42:48 CEST 2015

On Thursday 23 July 2015 08:00:20 Sze Howe Koh wrote:
> On 23 July 2015 at 01:03, Guido Seifert <wargand at gmx.de> wrote:
> >>> - the QObject's connections? Will all copies emit the same signals, will
> >>> all copies have their slots called?> 
> > Worked somehow... probably through magic.
> > 
> > This was my problem. It really looked like we could get away with it. The
> > whole class did not really need to be a QObject. It was only a QObject
> > because it was used from QML. The whole design was questionable.
> Qt 5.5 introduced Q_GADGET for this purpose. What's more, you can
> safely store a Q_GADGET inside a container.

Q_GADGET has existed since 4.0.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Interest mailing list