QTConcurrent run is async call, I tested this case on linux and the GUI is closed while the main process waited for the exporting thread to finish. I don't know how this will take place on different platforms, may be one who is familiar with QTconcurrent can help.
I thought if I could just print the exporting status to the status bar "Main error message widget" but I don't know if this breaks the convention as this bar is expected to be for errors only? regards, Gehad On Sat, Jan 31, 2015 at 2:59 AM, Dirk Hohndel <[email protected]> wrote: > On Fri, Jan 30, 2015 at 10:45:28PM +0200, Gehad Elrobey wrote: > > libxml2 consumes the main thread time while formatting the xml document. > So > > I attached a patch that calls the export function in a new thread. > > > > Now I am working on adding the progress bar functionality #785, but still > > can't interface with libxml2. > > What happens if the user quits after the export (but before the export is > finished)? > > /D > >
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
