Qt widget setParent

[Gopala Krishna]

QObjects store children as a list containing QObject pointers. When you delete the object or QObject destructor is called, it calls delete on all its children.

Now you can see the scenario in your case where you allocate QObjects on a stack and it does have parent. When parent is destructed , delete is called on object on stack which crashes your program.

edit: I was bit late(jpn answered first) but atleast better late than never

[bunjee]

I don't have any crash with my application .

My problem is memory.

According to Qt Doc :

Warning: It is very unlikely that you will ever need this function. If you have a widget that changes its content dynamically, it is far easier to use QStackedWidget.

Does setting parent to compromise anything for deletion I'm not aware off ?

[jpn]

It seems to prevent the widget from deletion, even when I'm calling delete widget, I'm not sure why.

What does this mean, actually? What do you mean with "prevent something from deletion"?

You're not the first to tell me so.

Indeed, seems you've been warned before in this thread by a bunch of people. Why do you insist doing it wrong? Have you seen any Qt examples allocating widgets or layouts on the stack (excluding main() and modal dialogs)? Or did you ever actually read any of them? Sorry for the tone, but I just don't understand people who regardless of continuous warnings insist of doing things their own (wrong) way.

My problem is memory.

What exact steps did you take to verify this?