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
ui/networking: do not skip the connected network #29396
ui/networking: do not skip the connected network #29396
Conversation
auto it = seenNetworks.find(ssid); | ||
if (it != seenNetworks.end()) { | ||
if (it.value().connected != ConnectedType::DISCONNECTED || it.value().strength >= strength) { | ||
continue; | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure this uses the max signal strength and still updates the connected status? if it's connected, it will always continue and never update the strength. perhaps we just update the Network in each section of this for loop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seenNetworks is cleared before loop. all items in it are update-to-date. never mind.I misunderstood
…t_skip_connected_network
|
||
SecurityType security = getSecurityType(properties); | ||
ConnectedType ctype = ConnectedType::DISCONNECTED; | ||
seenNetworks[ssid].security_type = getSecurityType(properties); | ||
if (path.path() == activeAp) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@deanlee looks like this is only true for the current access point, right? If so, does my change LGTY?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
thanks! |
resolve #28688