View Single Post
Old 11-12-2019, 10:42 PM   #7
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,887
Karma: 6120478
Join Date: Nov 2009
Device: many
Yes it is a modal dialog and by closing the Window that generated the modal dialog you went around its modal behaviour. Notice how you can not move the main Sigil window to cover the file dialog box or bring it to the foreground, indicating that this dialog must be dismissed first. The correct approach is to hit cancel in a modal dialog first (that is why it was made modal) then close the Window which is its parent if that is what you want to do. When you forcibly close its parent first, you leave it an orphan and Sigil is still running in the background but now without a main window.

FWIW, I am not sure this behaviour is what this issue was about. Yes, Qt should have prevented you from closing the Window without dismissing the dialog first but Qt has never handled that well on macOS.
KevinH is offline   Reply With Quote