Discarding this event may be interpreted as if the application doesn't
want to close the window and demands user interaction
This cancels shutdown on KDE, for example, despite application silently
quitting afterwards
Some things I'm not sure about:
I've removed check for isVisible() - I don't really understand what purpose did it serve. User can't really close invisible window and why would you call close on a hidden window and expect it behave differently? The only call to MainWindow::close() I've found is handling Quit shortcut.
I've replaced quit timer with sleep. IrcConnection seems to be closing fine while main thread is asleep and I don't think we want any other UI interaction while the app is quitting.
Discarding this event may be interpreted as if the application doesn't want to close the window and demands user interaction
This cancels shutdown on KDE, for example, despite application silently quitting afterwards
Some things I'm not sure about:
isVisible()- I don't really understand what purpose did it serve. User can't really close invisible window and why would you call close on a hidden window and expect it behave differently? The only call to MainWindow::close() I've found is handlingQuitshortcut.IrcConnectionseems to be closing fine while main thread is asleep and I don't think we want any other UI interaction while the app is quitting.