[Interest] Finished signal from QProcess!
lata.agrawal at enrouteinc.com
Tue Mar 6 11:47:36 CET 2012
On 1 March 2012 17:52, Mandeep Sandhu <mandeepsandhu.chd at gmail.com> wrote:
> > Yes, download is over a network. I used thread/process because download
> > process is very time consuming and I have to continuously check for other
> > kinds of downloads. Yes, I can download using QNetworkAccessManager but
> > then all download will have to be done in either a thread or a process
> > because it is time consuming.
> How does that matter? Even if the download takes long, becaue the QNAM
> API's are async, you will get a notification when a download
> completes. You can then use the req url, stored in the QNetworkReply
> object you got when you dispatched the request, to figure out which
> request got completed. I still don't see a case for a separate
> thread/process for just the download part (maybe I'm missing some
> Sorry for replying late. Whatever you have suggested above makes sense to
me. I will try that out. Thanks for all your help.
> > How can I use processEvents in my class process app events?
> Umm not sure what you meant here. Why do you manually need to call
> processEvents? Are you blocking your event loop somewhere or are you
> worried that the time-consuming download will block your event loop?
> (the download won't block your event loop).
> > Regards,
> > Lata
> >> -mandeep
> > --
> > Lata Agrawal
> > Senior Developer
> > 9699750643
> > En Route Media Pvt. Ltd.
En Route Media Pvt. Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest