Skip to content

Conversation

borntocompile
Copy link
Contributor

  • onProgress now uses null propagation before invoking.
  • onProgress now invoke with the correct value as a parameter

* onProgress now uses null propagation before invoking.
* onProgress now invoke with the correct value as a parameter
{
currentProgress = progress;
onProgress(downloadProgress);
onProgress?.Invoke(currentProgress = progress);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the assigning of currentProgress happening in the invocation does this mean it wont be assigned if onProgress event is null? if so then this would be incorrect functionality.

Moved the assigning of currentProgress out of the invokation of the onProgress event
@borntocompile borntocompile merged commit 345977d into development Sep 1, 2019
@kkjamie kkjamie mentioned this pull request Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants