QMdiSubWindow geometry and size save and restore
-
@mrjj Thank you for clarifying. Will test both. I never used event filters before, seems like a learning opportunity.
@artwaw
well event filters are handy for catching events from outside in cases where subclassing might be a bit invasive to existing code or subclassing would be a bit massive if many types of widgets are involved.That said, one has to take care not to eat events by accident.
-
@artwaw
well event filters are handy for catching events from outside in cases where subclassing might be a bit invasive to existing code or subclassing would be a bit massive if many types of widgets are involved.That said, one has to take care not to eat events by accident.
-
@mrjj Event filter works nicely when mdi sub window is closed and restored but there is one edge case:
when closing application with sub window open it is not called at all. Any hint you can offer how to get past that?@artwaw
Hi
Well i guess any open windows are just deleted, not closed as such, when whole app exits.One way could be to override closeEvent for the mainwindow and
loop over the windows (ui->mdiArea->subWindowList ) , calling close() on each
to have the event code handle it like they were manually closed. -
@artwaw
Hi
Well i guess any open windows are just deleted, not closed as such, when whole app exits.One way could be to override closeEvent for the mainwindow and
loop over the windows (ui->mdiArea->subWindowList ) , calling close() on each
to have the event code handle it like they were manually closed. -
@artwaw
Hi
Well i guess any open windows are just deleted, not closed as such, when whole app exits.One way could be to override closeEvent for the mainwindow and
loop over the windows (ui->mdiArea->subWindowList ) , calling close() on each
to have the event code handle it like they were manually closed. -
@mrjj but calling close() on each of opened sub windows doesn't call the eventFilter on any of them.
@artwaw
Hi
Ah yes. my bad. sorry. the close() function is a direct method.
So move the inner saving code to a function that takes a QMdiSubWindow *
and call that from closeEvent pr Window.You could also use
QCoreApplication::postEvent
to send a close to them. -
@artwaw
Hi
Ah yes. my bad. sorry. the close() function is a direct method.
So move the inner saving code to a function that takes a QMdiSubWindow *
and call that from closeEvent pr Window.You could also use
QCoreApplication::postEvent
to send a close to them.wrote on 13 May 2021, 11:42 last edited by@mrjj it's interesting how it doesn't work.
I tried both postEvent and sendEvent, the former with normal and high priority - to no avail.What's even more interesting for me here is that when mdi sub window is getting closed independently the internal widget's closeEvent() is being processed. When I just close the application with sub windows opened their closeEvent()s are not called at all - so implementing custom class based on QMdiSubWindow and overriding its closeEvent() makes no sense too.
I am truly puzzled now.
-
@mrjj it's interesting how it doesn't work.
I tried both postEvent and sendEvent, the former with normal and high priority - to no avail.What's even more interesting for me here is that when mdi sub window is getting closed independently the internal widget's closeEvent() is being processed. When I just close the application with sub windows opened their closeEvent()s are not called at all - so implementing custom class based on QMdiSubWindow and overriding its closeEvent() makes no sense too.
I am truly puzzled now.
wrote on 13 May 2021, 12:01 last edited byThis post is deleted! -
@mrjj it's interesting how it doesn't work.
I tried both postEvent and sendEvent, the former with normal and high priority - to no avail.What's even more interesting for me here is that when mdi sub window is getting closed independently the internal widget's closeEvent() is being processed. When I just close the application with sub windows opened their closeEvent()s are not called at all - so implementing custom class based on QMdiSubWindow and overriding its closeEvent() makes no sense too.
I am truly puzzled now.
wrote on 13 May 2021, 12:11 last edited byAll sorted. I made mistakes somewhere else and as a result closeEvent() of QMainWindow has not been called - once I fixed that everything works as per proposed solution with QCoreApplication::postEvent()
-
All sorted. I made mistakes somewhere else and as a result closeEvent() of QMainWindow has not been called - once I fixed that everything works as per proposed solution with QCoreApplication::postEvent()
@artwaw
Hi
excellent :)Just as a note. If you get very into Docks then please notice
https://github.com/githubuser0xFFFF/Qt-Advanced-Docking-Systemas It can dock to central/center, a feature which often is much loved when you want such setup.
13/13