On 17-04-2010 04:00, Yuki KODAMA wrote: > Thanks for digging concurrent features in PyQt, Adrian. > Meanwhile I'll do it with QThread class or others :-) > > "Future" mechanism is good, no doubt. But if we decide to use it, > it's difficult to refer our current GTK+ based implementation of > the application base which communicates with Mercurial. > It's a bit hard way, probably... :P > > BTW, does that Phil's email mean PyQt doesn't support QFuture* > classes in the future?
Well, we can easily make wrappers like that (Future) ourselves (where "we" doesn't imply "me" :-p), and we could do that for GTK as well. /Sune ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
