QT propose more public methods than MFC , for example it’s very easy to change
the background color of QT edit component and I remember that I spend
many times to do that with MFC. 

For Gui layer MFC propose more components but QT propose more functionalities.

Activex support:

COM technology is a good solution for many problems,
but unfortunately the misunderstanding of this technology makes it very complex
and many architects avoid it.

We have to consider COM technology only as a wrapper over POCO classes
to adapt them to be used with other languages, so this layer can be developed
by only one developer, the problem is that the development team makes COM
the kernel of the application and begins the development with them.

QT propose activeqt project to manage ActiveX but MFC has a complete
support for OLE and ActiveX than QT.


Networking support

QT propose classes for many khown networking protocols.



MFC support also all these protocols, and for this functionality QT is equal to MFC.

XML support:

QT gives classes to parse DOM and Sax, it's very simple to use and MFC treat
xml through COM components,So you have to know some automation basics
and types.
QT is easy to use than MFC when manipulating XML.

Design

QT is well designed than MFC, it use many patterns ,
for example data are in general isolated into classes which names end
with "Private" like QWidgetPrivate.

MVC Pattern

MFC propose CDocument/CView concept to implement MVC pattern, as explained in the latest post
avoid use CDocument as your model but only as controler.

MFC provide also functionalities like saving, printing, OLE embedding, and the Doc/View provide a design
of your application,but we have to be careful when using a technical framework that proposes an architecture;
it can makes the project less flexible.

For QT MVC is very used for gui components, let's take for example QPushButton and QRadioButton,
they use the same model QAbstractButton.

and we can also observe the existance of QStyle in this dependency graph,
so the Style is isolated to permit many look and feel.




And QT propose also the concept of signal and slot that makes easy the programming of event handling.

Abstractness vs Instability:

The "Abstractness vs Instability" graph can be useful to detect projects that will be difficult to maintain or evolve.
This following post describe the utility of this graph and how to exploit it to improve the design.

For QT here's the "Abstractness vs Instability" graph: