You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When downloading larger files via the generated API I miss a possibility to get the download progress. This could be achieved by connecting to the signal QNetworkReply::downloadProgress.
Describe the solution you'd like
I see two possible ways:
pass the QNetworkReply::downloadProgress to the clients
add a downloadProgress signal to the HttpRequest header
connect the QNetworkReply::downloadProgress to the new signal in the HttpRequest body right before the connect to QNetworkReply::finished
add a downloadProgress signal to the api-header and connect this in the api-body right before the connect to HttpRequestWorker::on_execution_finished
OR make the QNetworkReply available
add a parameter to a changeable reference pointer to the HttpRequest::execute that can be read in the client's major call (the first occurrence of nickname)
Solution 2 would make more interaction with the reply available but may also enable misusing it.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When downloading larger files via the generated API I miss a possibility to get the download progress. This could be achieved by connecting to the signal
QNetworkReply::downloadProgress
.Describe the solution you'd like
I see two possible ways:
QNetworkReply::downloadProgress
to the clientsdownloadProgress
signal to theHttpRequest
headerQNetworkReply::downloadProgress
to the new signal in theHttpRequest
body right before the connect toQNetworkReply::finished
downloadProgress
signal to the api-header and connect this in the api-body right before the connect toHttpRequestWorker::on_execution_finished
QNetworkReply
availableHttpRequest::execute
that can be read in the client's major call (the first occurrence of nickname)Solution 2 would make more interaction with the reply available but may also enable misusing it.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: