https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #6 from RJVB <rjvber...@gmail.com> --- To get this back to a hopefully more constructive state (and ignoring for the moment whether or not calling Qt API from a signal handler is an issue or not): what would be the best way to make the exit procedure as least block-prone and non-interactive as possible? Would it be enough to shunt the KSaveSelectDialog? And before I get in too deep: is there a reason behind the selection of signals currently connected to a graceful exit, IOW, are any of these sent in a context where it would NOT be OK to discard unsaved changes? -- You are receiving this mail because: You are watching all bug changes.
