Deleting Pointer to widget Qt C++

Question

I am new with Qt and i am very confused about how widgets are deleted. I was reading a video and i wanted to show up a QProgressbar while the video frames are being read and then remove this QProgressbar when the video is loaded.

I have done it with 2 different ways:

1. Using Pointers

    QWidget* wd = new QWidget(); QProgressBar* pB = new QProgressBar(wd); QLabel* label = new QLabel(wd); //setting geometry and updating the label and progressbar wd->deleteLater(); wd->hide(); 

   this code is written inside a class and i was assuming when the destructor of this class is called, the widget will be deleted with all of it's children but that didn't happen and everytime i run this function again a new widget is created without hiding or deleting the previous one (NOTE: i have tried to delete the label and progressbar from the widget assuming that they will disappear from inside the widget but this didn't happen "delete(pB);")

2. Using Objects

     QWidget wd; QProgressBar pB(&wd); QLabel label(wd); //setting geometry and updating the label and progressbar wd.deleteLater(); wd.hide(); 

When i have run the same code but using objects instead of pointers , it has run exactly as i have wanted and everytime i run the function, the old widget is destroyed and a new one is created.

NOTE: -Also when i close the main window, in case of pointers, the widget wd still exists and the program doesn't terminate until i close them manually - In case of Objects, when i close the main window everything is closed and the program is terminated correctly.

I need someone to explain me why is this happening and how if i am having a vector of pointers to widgets to delete all pointers inside that vector without any memory leakage

Answer 1

In typical C++ the rule would be "write one delete for every new ". An even more advanced rule would be "probably don't write new or delete and bury that in the RIAA pattern instead". Qt changes the rule in this regard because it introduces its own memory management paradigm. It's based on parent/child relationships. QWidget s that are new ed can be given a parentWidget() . When the parentWidget() is destroyed, all of its children will be destroyed. Hence, in Qt it is common practice to allocate objects on the stack with new , give them a parent, and never delete the memory yourself. The rules get more complicated with QLayout and such becomes sometimes Qt objects take ownership of widgets and sometimes they don't.

In your case, you probably don't need the deleteLater call. That posts a message to Qt's internal event loop. The message says, "Delete me when you get a chance!" If you want the class to manage wd just give it a parent of this . Then the whole parent/child tree will get deleted when your class is deleted.

Answer 2

It's all really simple. QObject -derived classes are just like any other C++ class, with one exception: if a QObject has children, it will delete the children in its destructor. Keep in mind that QWidget is-a QObject. If you have an instance allocated using QObject. If you have an instance allocated using new`, you must delete it, or ensure that something (a smart pointer!) does.

Of course, attempting to delete something you didn't dynamically allocate is an error, thus:

1. If you don't dynamically allocate a QObject , don't deleteLater or delete it.

2. If you don't dynamically allocate a QObject 's children, make sure they are gone before the object gets destructed.

Also, don't hide widgets you're about to destruct . It's pointless.

To manage widget lifetime yourself, you should use smart pointers:

class MyClass {
  QScopedPointer<QWidget> m_widget;
public:
  MyClass() :
    widget{new QWidget};
  {
    auto wd = m_widget->data();
    auto pb = new QProgressBar{wd};
    auto label = new QLabel{wd};
  }
};

When you destroy MyClass , the scoped pointer's destructor will delete the widget instance, and its QObject::~QObject destructor will delete its children.

Of course, none of this is necessary: you should simply create the objects as direct members of the class:

class MyClass {
  // The order of declaration has meaning! Parents must precede children.
  QWidget m_widget;
  QProgressBar m_bar{&m_widget};
  QLabel m_label{&m_widget};
public:
  MyClass() {}
};

Normally you'd be using a layout for the child widgets:

class MyClass {
  QWidget m_widget;
  QVBoxLayout m_layout{&m_widget};
  QProgressBar m_bar;
  QLabel m_label;
public:
  MyClass() {
    m_layout.addWidget(&m_bar);
    m_layout.addWidget(&m_label);
  }
};

When you add widgets to the layout, it reparents them to the widget the layout has been set on.

The compiler-generated destructor looks as below. You can't write such code, since the compiler-generated code will double-destroy the already destroyed objects, but let's pretend you could.

MyClass::~MyClass() {
  m_label.~QLabel();
  m_bar.~QProgressBar();
  m_layout.~QVBoxLayout();
  // At this point m_widget has no children and its `~QObject()` destructor
  // won't perform any child deletions.
  m_widget.~QWidget();
}