vpilo added a comment.
In D18621#402717 <https://phabricator.kde.org/D18621#402717>, @jgrulich wrote: > In D18621#402712 <https://phabricator.kde.org/D18621#402712>, @vpilo wrote: > > > But there are legit cases where this timeout is way too long for no reason. > > > > If you close the popup and reopen it before the NM timeout expires, then the first request will fail, no attempt will be made at redoing the scan, and you're stuck for 30 seconds with the same list. > > > 15 seconds. no, if your device takes 2s for a scan, and if you open the popup, close it and reopen it (causing a new scan request) before the 12s mark, the popup will wait 15 more seconds, totalling ~27s. It was just an extreme example. Regardless, it's still a huge delay, if you consider that any phone will take ~2s for a scan //but rescan every 3-4s// when you have the wifi settings open. > Then you can fix this instead. You can check last scan attempt and make it to scan a bit later. There is a property in NM::WirelessDevice::LastScan, you can see when the last scan was performed and once the applet is opened, do a scan as soon as possible when you are sure the attempt will not fail. I can find LastScan in the fd.o apidox, but not in NMQt... ?!? If NM didn't have this timeout, we could have chosen ourselves how to do it (e.g. waiting for LastScan to be 5s in the past, then scan again). But it's now somewhat frustratingly slow, and a button could save a few seconds of annoyance that usually instead result in the user losing their patience and turning wifi off and on instead. I know this whole proposal sounds silly.. for me this also is silly. This is however about improving the user experience in a few use cases, so I'm trying to mitigate it. REPOSITORY R116 Plasma Network Management Applet REVISION DETAIL https://phabricator.kde.org/D18621 To: vpilo, #vdg, #plasma, jgrulich, ngraham Cc: alexeymin, plasma-devel, jraleigh, GB_2, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
