jgrulich added a comment.

  In D18621#402768 <https://phabricator.kde.org/D18621#402768>, @davidedmundson 
wrote:
  
  > > I can find LastScan in the fd.o apidox, but not in NMQt... ?!?
  >
  > It doesn't seem to be there. So lets add it.
  
  
  It's not there because it's most likely one of recent additions, which means 
we will not be able to rely on that if it's not in NM 1.4, or alternatively we 
will need to bump required NM version.
  
  In D18621#402766 <https://phabricator.kde.org/D18621#402766>, @ngraham wrote:
  
  > Again, I think this is a "the user doesn't feel in control" issue. If a 
feature of the software cannot automatically anticipate and meet user needs 
with 100% reliability, then the user must be provided with a method to 
self-serve for the cases where the software 's automatic behaviors are 
insufficient.
  
  
  Then make it reliable. If it's realiable and as I mentioned there can be some 
improvements done, you will provide them a functionality which in most cases 
will give them just false feeling that they changed something. Nobody will need 
to wait 15 seconds, because scanning is done everytime you open the applet and 
browse your connections. I believe that majority of users will hit the button 
right after they open the applet, while there is scanning being done and they 
have the feel to hurry things up, while actually it will do nothing.
  
  > In theory, refreshing upon open and every 15 seconds after that should be 
sufficient. But if for some reason it's not, then without a refresh button, the 
user doesn't feel in control and loses confidence in your software, and then 
they get upset and start filing nitpicky bugs and complaining on Reddit.
  
  I did receive just one bug for this and after I explained that this is done 
automatically on the background, the reporter didn't complain.
  
  I don't want to keep adding things to a small applet to cover every single 
use case. I know it's just a small button, but next time it will be another 
button, search bar or anything else and the applet will become a monster as it 
used to be in KDE 4 times. When we were developing this applet back then with 
Björn and Thomas, the idea wasn't to make everyone happy, that's not really 
possible, but it shouldn't make anyone unhappy, which I think this really 
doesn't.

REPOSITORY
  R116 Plasma Network Management Applet

REVISION DETAIL
  https://phabricator.kde.org/D18621

To: vpilo, #vdg, #plasma, jgrulich, ngraham
Cc: davidedmundson, alexeymin, plasma-devel, jraleigh, GB_2, ragreen, Pitel, 
ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart

Reply via email to