View Single Post
Old 02-18-2010, 09:33 AM   #24
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,082
Karma: 315558332
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by kovidgoyal View Post
d.setModal(False)

before the call to exec_
This does make the dialog non-modal, but it doesn't allow exec_() to return until after the OK button has been pressed - so an error still blocks the import.

It seems to be that I really need to be able to put the message box into its own thread or something. But reading up on QT in python, is seems to be the case that all GUI interactions must be in the main thread.

Thanks for all your suggestions. I think that warning of the problem is more important than not interrupting a large import, so I'll stick to the modal dialog for now.
pdurrant is offline   Reply With Quote