I guess your testroot inherits QWidget? In that case it has to have a similar constructor to your CQp class and you have to call that constructor.

You guessed right, but I don’t understand what you mean.

Thanks!

Do you have any good reference book that talks about this kind of inheritance? My code now compiles, but I haven’t the slightest idea why. I read about inheritance before, but it’s always demonstrated in simple cases, and rarely with abstract classes.

Thanks, @loladiro!

Joey Dumont wrote:

and when I try to compile, it complains that ‘QWidget’ is not a direct base of CQp. True. But I if make it a parent class to CQp explicitly, it complains that class CQp inherits QWidget from two places. Is there a way around that?

What the compiler is telling you is that from a constructor you can call only direct base constructors.

That is, if you have an inheritance chain like this

The offending line is obviously the call to the QWidget ctor here, since “testcase” is a direct base for CQp, and QWidget is a non-direct base:

Joey Dumont wrote:

1. #include "cqp.h"
2.  
3. CQp::CQp(QWidget *parent) :
4.     QWidget(parent)
5. {
6. }

And by using,

what am I changing to the inheritance chain?

You’re not changing the inheritance graph (which is defined by the class definition); that’s a call to a base constructor from your constructor. You’re now calling a costructor of a direct-base (allowed) instead of a non-direct base (forbidden).

Nothing, but you are calling the constructor of your base class (which is the only constructor your are allowed to call in C++).

Thanks for both your simultaneous answers!

Now, will I be able to instantiate the tests that are at the far end of the inheritance graph by using QWidget signals like show() and such? My guess is no, but if so my abstract classes organization scheme falls apart.

Any thoughts?

Yes you will! Signals/Slots are inherited just like methods (because they are methods).

Oh, I just got it. Thanks for your patience!