Thread related problems with QNetworkAccessmanager

[Moschops]

The bigger picture is that this is part of a much larger process that takes a long long time, and this network use happens in the middle of it. To avoid freezing the GUI, this larger process happens in a different thread and provides updates to the GUI so the GUI can have a nice progress bar and tell the user interesting things about what is happening.

So it sounds like I need to have this process still happen in a different thread, but instead of having it do its own

QNetworkReply *reply = _manager->get(request_);

QNetworkReply *reply = _manager->get(request_);

To copy to clipboard, switch view to plain text mode 

I need this secondary, non-GUI process to emit a signal that then causes

QNetworkReply *reply = _manager->get(request_);

QNetworkReply *reply = _manager->get(request_);

To copy to clipboard, switch view to plain text mode 

to happen in the main thread, and have the secondary process then wait around until the reply object emits a signal saying it's finished?