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

Sze Howe Koh szehowe.koh at gmail.com
Thu Jul 23 02:00:20 CEST 2015

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.

Note that Q_GADGET doesn't support signals and slots though.


More information about the Interest mailing list