yes, in the commit rev11997 I removed the Task Runner in Annotator, but it is not for that problem I met (which is temporarily calmed down by commenting out the 'addDockWidget').
I replaced the Task Runner with QProcess::execute to check whether the second one can execute .py executable file in Annotator. The answer is NO. By the way, you used to suggest the second: "Maybe using taskRunner is not such a good idea, because it makes the whole thing asyncronous, meaning that while saving, the user can manipulate the descriptors, and you have to deal with the state when the task is done, which is complex...." The Task Runner can be reverted, if needed? Maybe that problem can be fixed by the replacement. I'll try it anyway. (intending to sacrifice this sunday to gain the commit rev12000!!) ----- Original Message ----- From: "David García Garzón" <[EMAIL PROTECTED]> To: "Jun Jun" <[EMAIL PROTECTED]>; <[email protected]> Sent: Sunday, August 17, 2008 2:43 AM Subject: Task Runner removed?
_______________________________________________ Clam-devel mailing list [email protected] https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
