Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't require app restart when changing the use_median setting #476

Merged
merged 1 commit into from
Jun 2, 2024

Conversation

vmiklos
Copy link
Owner

@vmiklos vmiklos commented Jun 2, 2024

Have the getAfterLive() and the liveDataBoolean("use_median", ...) calls
in separate scopes, so in case we want to add more settings there in the
future, then no need to increase nesting again this way.

And in case afterSleep is not a callable, then it would be only called
once, so the chained LiveData wouldn't update properly.

Fixes #474.

Have the getAfterLive() and the liveDataBoolean("use_median", ...) calls
in separate scopes, so in case we want to add more settings there in the
future, then no need to increase nesting again this way.

And in case afterSleep is not a callable, then it would be only called
once, so the chained LiveData wouldn't update properly.

Fixes <#474>.
@vmiklos vmiklos enabled auto-merge (rebase) June 2, 2024 13:18
@vmiklos vmiklos merged commit e65f40a into master Jun 2, 2024
2 checks passed
@vmiklos vmiklos deleted the private/vmiklos/master branch June 2, 2024 13:25
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.

Changing calculation method from mean to median necessitates forced app reinitialization.
1 participant