@p3c0 Thanks!

@richardo I appreciate your input. Still I'm not sure I really like this approach that much better. As for the cycle, I couldn't see any of those usual cyclic property warnings that QML gives you in those cases. I think this cycle is already properly broken by using the correct construction in setMyCppValue: void setMyCppValue(int newValue) { if (newValue!=myCppValue) { myCppValue = newValue; emit myCppValueChanged(); } }

@Fred-Waltzer MyQMLObject will be available in all the QML files of the project. So no need to create different C++ variable.

@themts Hmmm that sounds really odd, but without the code, I don't know why it would output that error. I will say that you do not need a copy constructor. You could make a new qml type from class Thing : public QObject { Q_OBJECT public: explicit Thing(QObject* parent = nullptr); virtual ~Thing(); };