This repository has been archived by the owner on Aug 17, 2020. It is now read-only.
Don't create a new update timer if one already exists, #41 #46
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
Check for the _updateDataTimer to see if there already is one before creating an new one.
|
Merged, thanks. To be honest I'm being overrun by all the issues and I'm missing something :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This does not fix #41 %100.
There is still one issue where leaving a pokestop or battle forces a refresh. Then if the timer causes a refresh too soon after it will refresh with no pokemon or stops found. However, that will correct itself in 10sec after the next refresh occurs.