This repository was archived by the owner on Jun 22, 2023. It is now read-only.
Fix date going back if ElapsedTime overflows - #3
Open
ShadowGry wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On some sound level meters, the
ElapsedTimesequence overflows only after reaching 86,400 seconds (24 hours). IflastTimeis formatted to show the date, then it will suddenly change back to the date of when the stream was started when overflow occurs.When this happens, the
StartTimesequence is updated to the current time. It can be used with the overflowed values of theElapsedTimesequence to always get the correct date. Removing the condition that__startTimecan only be set once achieves this.