Why should a removeSubWindow() raise exception?

[jpn]

Usually QMdiSubWindows have Qt::WA_DeleteOnClose set which means they'll get deleted upon close event.

[Raccoon29]

Usually QMdiSubWindows have Qt::WA_DeleteOnClose set which means they'll get deleted upon close event.

Thank you, yes, now it is bright!

Update from the solving:
I tried to comment the row that raised the error (removeSubWindow()), and now everything works fine; I set the Qt::WA_DeleteOnClose so maybe when closing the window it got deleted, and when the method tried to remove it with the function, it found a deallocated memory: dump.
But now I'm wondering about the usefulness of the method removeSubWindow()... removing it, I don't risk memory lacks or something? The problem doesn't exist if what I just said is right, and DeleteOnClose works for it...

Anyway thank you very much,
you guru members make this forum unbeatable!

[Raccoon29]

I have another question that I think is related to this thread, so I didn't start a new one.

A Qt::WA_DeleteOnClose for a MdiSubWindow, when the subwindow get closed with event->accept() (in closeEvent()), deletes the QMdiSubWindow, or the QWidget inside it, or both of them??

[jacek]

A Qt::WA_DeleteOnClose for a MdiSubWindow, when the subwindow get closed with event->accept() (in closeEvent()), deletes the QMdiSubWindow, or the QWidget inside it, or both of them??

If that attribute was set for MDI subwindow, it will delete the subwindow and all child widgets.

[Raccoon29]

If that attribute was set for MDI subwindow, it will delete the subwindow and all child widgets.

Ok. Thank you jacek.