Since you're explicitly calling QDebug operator<<(QDebug &stream, const base &obj) the compiler can't call the other function. What you can do is to write your own "virtual QString debug() const" function in every class which you the call within the debug stream operator function. But once again - plain C++ :)

Hi As long as you dont do multiple inheritance , i think you base class design should work just fine. However, make sure to overrride int QGraphicsItem::type() const pr concrete class to make sure qgraphicsitem_cast() works.

@SGaist I sincerely want to thank you for your help! This project took six-months and your assistance was crucial in getting over the goal line in the final week. If I missed that hard deadline my six-month contract-to-hire would have been terminated. Partly because of your assistance I made it work and was hired full-time permanent! We shipped Version 1.0 and two weeks later I delivered a significant V1.1 follow up!. I momentarily had it setup as a (static?)linked library but backtracked to direct #includes from the /common/ folder, mainly because I understood it better. I intend to switch again to the library method because of compile times as you suggested. I was also scared off by an article suggesting I would need to add C++ #EXTERN statements, etc. to create a public interface for the library. Is that true, or can the .pro/.pri files define that folder as a library with NO changes to the C++? I still have to migrate *.qml files to the /common/ but I assume it's basically the same pattern as the C++. I haven't replied because I thought I had more questions but the project has been moving too rapidly. Thank you!

@mrjj said: but does QSslSocket not inherited QTcpSocket ? Yes, you're right thank you !

Hi, QObject is a non copyable type. See here for more information.

Hi Just a note first Having class SerialPort : public QObject and then QSerialPort *serialPort; Where only diffence is capital S to the main class is just confusing. anyway, why is the issue with settings(new SettingsDialog()), did you declare it as void settings(SettingsDialog *mydialog) Im not sure what you dont understand. To use a pointer to a class in another class, you simply give the pointer to the other class and it can use it class B {}; class A { B* mykeptBpointer; setB(B* myb) { mykeptBpointer = myb; } void DoB { mykeptBpointer->xxxx(); }; A mya; B* myb = new B; mya.setB(b); oh, is settings(new SettingsDialog()) rather settings = new SettingsDialog();

The Q_OBJECT macro can be put in public, protected or private section and it will do the same. It doesn't matter for moc but I highly recommend to always put it at the top of your class for the following reason: The Q_OBJECT macro is defined like this: #define Q_OBJECT \ public: \ //stuff... \ private: \ //other stuff... So it's easy to make your other members private by mistake like this: class Foo { public: Q_OBJECT int bar; //oh no! bar is private }; If you put the macro at the top it won't affect access declarations below: class Foo { Q_OBJECT public: int bar; //yes! bar is public as intended };

@bck25 ,@Frime Thank you all for the replies. I can not set the alpha value as I am using an image as the background. I solved this by moving the opacity to the BorderImage which acts as background of the Window. Window { id : root flags: Qt.FramelessWindowHint visible:true color: "transparent" // This works properly when Aero theme is enabled in Windows BorderImage { visible:true width:root.width height:root.height opacity: 0.8 source: "background.png" } }

Oh, I see. Thank you sir.

If your question was how to initialize QObject from child you do not need extra Parent variable, no extra deletes, just add it in constructor: Contact::Contact(int cat,QString fir,QString lst,QString ad,QString zp, QString ct,QString nm,QObject *parent) ::QObject( parent ) { .......... }

@Chris-Kawa I am building from within Qt Creator (Windows 7), my .pro file didn't contain that! it just had: QT += gui Thank you Chris.