Timeline for QNetworkReply wait for finished
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28 at 16:53 | comment | added | ManuelSchneid3r | Note that QApplication::quit() will leave the loop without having a finished reply. | |
| May 10, 2012 at 11:30 | comment | added | Kamil Klimek | It only means that you should consider connecting to some additional signals. It doesn't matter if it "always get called for me". There may be situation (as the docs say) when you won't get finished() signal, so your event loop will be stuck | |
| May 10, 2012 at 0:06 | comment | added | chikuba | havent come across any situation where the finished slot wasent called. i know that the doc states that it usally gets called but for me it always gets called | |
| Feb 14, 2012 at 9:24 | comment | added | Alexis Wilke | Also the other answer also includes mention of QEventLoop, this answer was correct at once. | |
| Mar 31, 2011 at 13:29 | vote | accept | yolo | ||
| Mar 31, 2011 at 13:29 | vote | accept | yolo | ||
| Mar 31, 2011 at 13:29 | |||||
| Mar 31, 2011 at 7:20 | history | answered | Kamil Klimek | CC BY-SA 2.5 |