This repository has been archived by the owner on Feb 4, 2023. It is now read-only.
fix: using random CH for non-password use too #118
Closed
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
|
too many changes :( my bad |
|
Hi @slaesh The new ESPAsync_WiFiManager v1.15.1 has just been released. Your contribution is noted in Contributions and Thanks Best Regards, Releases v1.15.1
|
khoih-prog
added a commit
to khoih-prog/ESP_WiFiManager
that referenced
this pull request
Oct 25, 2022
### Releases v1.12.1 1. Using random channel for softAP without password. Check [fix: using random CH for non-password use too #118](khoih-prog/ESPAsync_WiFiManager#118) 2. Add astyle using `allman` style. Restyle the library
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.
due to the fact that the
yieldwas AFTER the processing of connect and stop flag.. the loop would keep on for one last check.BUT, if we modify the timeout in our handlers, the loop may stop WITHOUT handling our flags..