Hi,
I find it sometimes helpful when access points appear and disappear (or
are at an extreme range). The network manager appears to get confused.
As a further incantation, I also turn off the radio and turn it back on.
So the 'discard' button has psychological advantages in working with a
frustrating network environment. (Although in truth, the only real cure
seems to be a cold start).
Tony
On 01/22/2014 01:41 AM, sugar-devel-requ...@lists.sugarlabs.org wrote:
To: Daniel Narvaez <dwnarv...@gmail.com> Cc: Frederick Grose
<fgr...@gmail.com>, "sugar-devel@lists.sugarlabs.org"
<sugar-devel@lists.sugarlabs.org> Subject: Message-ID:
<20140121233155.gg23...@us.netrek.org> Content-Type: text/plain;
charset=us-ascii On Wed, Jan 22, 2014 at 12:24:31AM +0100, Daniel
Narvaez wrote:
>Before we go further discussing implementation, could someone
>explain why we need a global "Discard wireless connections" button
>vs the "Forget" item in the device palette which someone has mostly
>implemented already?
Does "Forget" forget all networks, not just the ones present?
Otherwise, the only reason I can think of is the installed base
expectations and training issues.
If I recall correctly, the main use case was inability to properly
handle access points that either changed their passphrase or switched
between encrypted and not-encrypted. If you add these test cases and
pass them, I see no major problem with removing "Discard...".
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
