Interfaces must inherit QObject?!
-
It seems to me that for a class where you inherited perhaps a set of interfaces and one QObject, you can't inherit any other QObject class. e.g.
class RealCake: public QObject, public ICake, public IEdible{} class PlasticCake: public QObject, public ICake {} class JokeCake: public PlasticCake, public RealCake{}The
JokeCakeis not allowed in the world of Qt. Pity!@idlefrog said in Interfaces must inherit QObject?!:
The JokeCake is not allowed in the world of Qt. Pity!
Even if it were allowed, you're using it incorrectly. C++ is hard, man, it's just the way it is.
-
It seems to me that for a class where you inherited perhaps a set of interfaces and one QObject, you can't inherit any other QObject class. e.g.
class RealCake: public QObject, public ICake, public IEdible{} class PlasticCake: public QObject, public ICake {} class JokeCake: public PlasticCake, public RealCake{}The
JokeCakeis not allowed in the world of Qt. Pity!@idlefrog
Yes indeed that is precisely my understanding (unless mistaken). You must not inherit multiple times fromQObejct, whether directly or indirectly, and regardless of order. Because of moc requirement/limitation.I still refer you back to QObject Multiple Inheritance. Ah, hang on, I think the solution I had in mind is at https://stackoverflow.com/a/18113601/489865 "the Qt way of doing this is like this...." But now I see that includes
I am amazed that this actually works, but bummed out by the fact that it requires the old-style SIGNAL()/SLOT() syntax...
[Not my language!] Which is a bu**er :(
-
@idlefrog
Yes indeed that is precisely my understanding (unless mistaken). You must not inherit multiple times fromQObejct, whether directly or indirectly, and regardless of order. Because of moc requirement/limitation.I still refer you back to QObject Multiple Inheritance. Ah, hang on, I think the solution I had in mind is at https://stackoverflow.com/a/18113601/489865 "the Qt way of doing this is like this...." But now I see that includes
I am amazed that this actually works, but bummed out by the fact that it requires the old-style SIGNAL()/SLOT() syntax...
[Not my language!] Which is a bu**er :(
@JonB said in Interfaces must inherit QObject?!:
I still refer you back to QObject Multiple Inheritance. Ah, hang on, I think the solution I had in mind is at https://stackoverflow.com/a/18113601/489865 "the Qt way of doing this is like this...." But now I see that includes
This is simply an abomination. Signals act polymorphically without the need to declare them as pure virtual in interfaces. Slots are a different kettle of fish, they work just fine with overriding.
(Edit)
Addendum:Yes indeed that is precisely my understanding (unless mistaken). You must not inherit multiple times from QObejct, whether directly or indirectly, and regardless of order. Because of moc requirement/limitation.
Just to spill it as explicitly and bluntly as I possibly can:
You shall not derive a class from the same base multiple times (directly or indirectly) if you don't intimately know what's the difference between:class Derived : public Baseand
class Derived : virtual public BaseRead and abide by the Qt Code of Conduct
-
@JonB said in Interfaces must inherit QObject?!:
I still refer you back to QObject Multiple Inheritance. Ah, hang on, I think the solution I had in mind is at https://stackoverflow.com/a/18113601/489865 "the Qt way of doing this is like this...." But now I see that includes
This is simply an abomination. Signals act polymorphically without the need to declare them as pure virtual in interfaces. Slots are a different kettle of fish, they work just fine with overriding.
(Edit)
Addendum:Yes indeed that is precisely my understanding (unless mistaken). You must not inherit multiple times from QObejct, whether directly or indirectly, and regardless of order. Because of moc requirement/limitation.
Just to spill it as explicitly and bluntly as I possibly can:
You shall not derive a class from the same base multiple times (directly or indirectly) if you don't intimately know what's the difference between:class Derived : public Baseand
class Derived : virtual public Base@kshegunov
Yeah, I didn't notice thevirtualon the signal. That's the trouble with assuming an accepted solution with 60 up-votes must be good!It shows a lot of people are obviously struggling with this. How then can the OP here arrange to write an "interface" which inherits from
QObjectand apply it to classes which inherit fromQObjecttoo?Ohhhh, maybe I misunderstood? Only now do I see that OP did not originally say that
ICakeneededQObjectitself. Only that he put it first in the class inheritance list beforeQObjectand that upset moc. I get it now, and whypublic QObject, public ICakeworks here. OK, but what about if OP did want multipleQObjectinheritance, any way without the "abomination" ? -
@kshegunov
Yeah, I didn't notice thevirtualon the signal. That's the trouble with assuming an accepted solution with 60 up-votes must be good!It shows a lot of people are obviously struggling with this. How then can the OP here arrange to write an "interface" which inherits from
QObjectand apply it to classes which inherit fromQObjecttoo?Ohhhh, maybe I misunderstood? Only now do I see that OP did not originally say that
ICakeneededQObjectitself. Only that he put it first in the class inheritance list beforeQObjectand that upset moc. I get it now, and whypublic QObject, public ICakeworks here. OK, but what about if OP did want multipleQObjectinheritance, any way without the "abomination" ?@JonB said in Interfaces must inherit QObject?!:
OK, but what about if OP did want multiple QObject inheritnace, any way without the "abomination" ?
He shan't do it. Also read the addendum I added to my previous post.
Read and abide by the Qt Code of Conduct
-
@JonB said in Interfaces must inherit QObject?!:
OK, but what about if OP did want multiple QObject inheritnace, any way without the "abomination" ?
He shan't do it. Also read the addendum I added to my previous post.
@kshegunov
Is that a requirement of C++? The OP claimedclass VictoriaSpongeCake : public ICake, public QObjectSo if I change
ICaketo inherit like this:class ICake: public QObjectIt all compiles without a problem.
That is not quoting me, it is quoting him.
-
@kshegunov
Is that a requirement of C++? The OP claimedclass VictoriaSpongeCake : public ICake, public QObjectSo if I change
ICaketo inherit like this:class ICake: public QObjectIt all compiles without a problem.
That is not quoting me, it is quoting him.
@JonB said in Interfaces must inherit QObject?!:
Is that a requirement of C++?
It is not a requirement, but there's a significant difference.
Here's links, I know you love them sources:
https://isocpp.org/wiki/faq/multiple-inheritance (What is the “dreaded diamond”? being key)
https://en.cppreference.com/w/cpp/language/derived_class (Virtual base classes is relevant)Read and abide by the Qt Code of Conduct
-
@JonB said in Interfaces must inherit QObject?!:
Is that a requirement of C++?
It is not a requirement, but there's a significant difference.
Here's links, I know you love them sources:
https://isocpp.org/wiki/faq/multiple-inheritance (What is the “dreaded diamond”? being key)
https://en.cppreference.com/w/cpp/language/derived_class (Virtual base classes is relevant)@kshegunov
Yeah, thanks, this looks good.public virtual Base, that's a new one for me, I like it. The more complexity in C++ the better... ;-) -
@kshegunov
Is that a requirement of C++? The OP claimedclass VictoriaSpongeCake : public ICake, public QObjectSo if I change
ICaketo inherit like this:class ICake: public QObjectIt all compiles without a problem.
That is not quoting me, it is quoting him.
@JonB said in Interfaces must inherit QObject?!:
@kshegunov
Is that a requirement of C++? The OP claimedclass VictoriaSpongeCake : public ICake, public QObjectSo if I change
ICaketo inherit like this:class ICake: public QObjectIt all compiles without a problem.
That is not quoting me, it is quoting him.
OP forgot to re-run
qmake(or delete the build directory) after makingICakeinherit QObject and adding theQ_OBJECTmacro.@JonB said in Interfaces must inherit QObject?!:
How then can the OP here arrange to write an "interface" which inherits from
QObjectand apply it to classes which inherit from QObject too?They can't.
QObjects are designed to be "identity objects", as opposed to "value objects": https://doc.qt.io/qt-5/object.html#qt-objects-identity-vs-value (for example, an image is a value but a window is an identity). I'd say that an "interface object" is neither an identity nor a value.
One more thought: If a class inherits from 2 differnent QObjects, what should
obj->staticMetaObject.superClass()return?P.S. I think you'll enjoy the thoroughness of this article: https://www.ics.com/blog/multiple-inheritance-qt
Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
-
@JonB said in Interfaces must inherit QObject?!:
@kshegunov
Is that a requirement of C++? The OP claimedclass VictoriaSpongeCake : public ICake, public QObjectSo if I change
ICaketo inherit like this:class ICake: public QObjectIt all compiles without a problem.
That is not quoting me, it is quoting him.
OP forgot to re-run
qmake(or delete the build directory) after makingICakeinherit QObject and adding theQ_OBJECTmacro.@JonB said in Interfaces must inherit QObject?!:
How then can the OP here arrange to write an "interface" which inherits from
QObjectand apply it to classes which inherit from QObject too?They can't.
QObjects are designed to be "identity objects", as opposed to "value objects": https://doc.qt.io/qt-5/object.html#qt-objects-identity-vs-value (for example, an image is a value but a window is an identity). I'd say that an "interface object" is neither an identity nor a value.
One more thought: If a class inherits from 2 differnent QObjects, what should
obj->staticMetaObject.superClass()return?P.S. I think you'll enjoy the thoroughness of this article: https://www.ics.com/blog/multiple-inheritance-qt
