Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Don't wowwy though, I got it all mapped out!
It's like this, some senpai wwote the function
twice! One such case is when simply changing an adaptor.
main/Manager.py wesponds to this signal by calling display_known_devices in gui/DeviceList.py, twice! add_device in gui/DeviceList.py is then called twice too, which then calls the sauce of the pwoblem, monitor_power_levels in gui/DeviceList.py.
So the first timer gets removed and we never get to know how stwong the signal actually is, because there is no timer that cares for it because of the cache. The super fast self.monitored_devices cache pwevents display_known_devices from being idempotent!!! You senpais can either wemove the cache or make sure to call display_known_devices only once, but as it stands, once we change between two adapters, we can't see which device is actually connected and how strong that connection is!!!!!!!!
That is all I wanted to so, I hope you can be so nice to
@KrzysztofSzewczyk you seem confused, let me help you.
@MikuChan03 identified an issue with signal bars when switching adapters. Next found the cause of the signal bars disappearing and pointed where to look. So thanks to @MikuChan03 I was able to quickly find the bug and fix it. I'm sure you see why I appreciate the contribution and we should thank @MikuChan03!