Home/ Questions/Q 661407
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T23:15:49+00:00

Sorry for the dumb question, but I’m working with Qt and C++ for the

  • 0

Sorry for the dumb question, but I’m working with Qt and C++ for the first time, and working through the tutorial and some samples.

One thing that was mentioned was that Qt stuff doesn’t need to be explicitly deleted. So, main question, does this also apply to collections of Qt stuff? Like say I want a dynamic number of MyWidgets, so I keep a vector or whatever of them. Are they still taken care of for me?

As a side question, what is going on to make it so I don’t have to worry about destructors?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Qt has an interesting object model for sure. When I first started it made me uneasy that there were so many new Foo calls and no deletes.

    http://qt.nokia.com/doc/4.6/object.html Is a good place to start reading up on the object model.

    Things of interest:
    QObject subclasses have their assignment and copy-ctor methods disabled. The chain of object child-parents is maintained internally by QObject.

    Generally when instantiating a QObject subclass (if you don’t plan on managing its pointer yourself) you will provide another QObject pointer as the parent. This ‘parent’ then takes over the management of the child you just made. You can call setParent() on a QObject to change who “owns” it. There are very few methods in Qt that will change the parent of an object, and they all explicitly state that they do in the docs.

    So to answer your specific question: it depends on how you made all of your MyWidget instances.

    If you made each one with a parent, then no you don’t have to delete them. The parent will delete them when it gets deleted.

    If you’re keeping a QList<MyWidget*> collection of them, and you didn’t give them a parent, then you should delete them yourself.

    • 0