a>: 如果您使用多重继承, moc假设第一个 inherited类是QObject 。此外,请确保只有的第一个继承类是QObject 。 建议使用更像代理模式的东西,或者用HasA而不是IsA关系重新创建。 I am trying to use mix in classes for C++/Qt to provide a whole bunch of widgets with a common interface. The interface is defined in such as way so that if it is defined as the base class for other widget classes, then the widget themselves will have those signals. ie refer below. class SignalInterface: public QObject { Q_OBJECT public: SignalInterface(); virtual ~SignalInterface(); signals: void iconChanged(QIcon); void titleChanged(QString);}class Widget1: public SignalInterface, QWidget{ public: Widget1() virtual ~Widget1() // The Widget Should Inherit the signals}Looking at the class hierarchy the problem becomes apparent, I have stumbled on to the dreaded diamond in Multiple Inheritance, where the Widget1 inherit from QWidget, and SignalInterface, and both which inherit from QObject. Will this cause any issues?We know that this problem can be easily solved if the QObject class is pure virtual (which is not the case).A possible solution would be class Interface: public QWidget {Q_OBJECTsignals:void IconChanged(QIcon);void titleChanged(QString);}class Widget1: public Interface {}The issue here is that I already have lot of code that inherit from QWidget, and its painful to hack that in. Is there another way? 解决方案 Unfortunately inheriting QObject twice will cause problems in moc.From http://qt-project.org: If you are using multiple inheritance, moc assumes that the first inherited class is a subclass of QObject. Also, be sure that only the first inherited class is a QObject.I would suggest using something more like the delegate pattern, or recreate with a HasA not a IsA relationship. 这篇关于QObject多重继承的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!
08-24 17:22
查看更多