g_iAwayCounter clearing restrictions when nothing has changed #1110
Conversation
This file contains 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
8.3 features branch
…ng has changed When leasher is away, realleash keeps spamming the collar with messages every 10 seconds when nothing has changed. Change should not be noticalbe to wearer, just test that leasher detection works correctly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When leasher is away, realleash keeps spamming the collar with messages every 10 seconds when nothing has changed.
Technically when leasher is away we call ApplyRestrictions() and set g_iAwayCounter to -1. We dont need to call ApplyRestrictions() again until leasher is in range, and g_iAwayCounter set larger than 0.
Change should not be noticalbe to wearer, just test that leasher detection works correctly.