The discussion is veering away from the initial complaint -- where the user's action may cause an unintentional disconnect from the network. Fortunately, there is a single solution to everyone's problem: Add a RadioButton for a "None" option.
This gives us the ability to: - Select None to disconnect from a wireless network that is already connected Once we have a "None" option, that is how a user can "reconnect" as well: First select None to disconnect, then select the the wireless network they wanted to reconnect to. Additionally, having a "None" fixes another quirk. Currently when starting up and no wireless networks are connected, none of the RadioButton options is selected. Having a "None" button clears this up as well. Here's more to my argument about "reconnect" being a misuse of a RadioButton interface: "A gtk.RadioButton is used to give the user a choice of one of many options." I took that from the GNOME Documentation Library: http://library.gnome.org/devel/pygtk/2.12/class-gtkradiobutton.html Using a RadioButton interface to do more than a simple "choose one of many options" makes the user interface inconsistent. This causes an inconsistency even within the NetworkManager app -- as selecting a RadioButton for the VPN Connections option that is already connected DOES NOT reconnect to that VPN (see Bug# 141568 where I reported this inconsistency). -- Clicking on already-selected Wired Network causes disconnect https://bugs.launchpad.net/bugs/86186 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
