If the wireless device doesn't support either of the two possible
hotspot modes, disable the button. Also, add a tooltip to the button
when it's disabled, explaining why ("device does not support" or
"system policy prohibits").
https://bugzilla.gnome.org/show_bug.cgi?id=675317
For disconnected/unavailable devices, show the localized
NMDeviceStateReason next to the localized NMDeviceState (and not in
the tooltip). Also, move the code to do this into panel-common rather
to save some duplication.
https://bugzilla.gnome.org/show_bug.cgi?id=676117
Use the 'image-button' style class to make symbolic buttons square
(as supported by latest Adwaita), and make sure to use the correct icon
size for all symbolics to avoid fuzzyness.
https://bugzilla.gnome.org/show_bug.cgi?id=693357
Recent NetworkManager can create AP-mode hotspots instead of Ad-Hoc
mode ones, which are less compatible with mobile devices. Do that
if NetworkManager and the device support it.
https://bugzilla.gnome.org/show_bug.cgi?id=686732
In addition to simplifying a bunch of places that were calling
nm_remote_settings_list_connections() +
nm_device_filter_connections(), this also ensures we filter out slave
connections everywhere (except when they are the active connection).
https://bugzilla.gnome.org/show_bug.cgi?id=677145
This code is fairly independent of the rest, and we don't want
net-device-wifi.c to become too massive and unmaintainable.
The code in connection-editor/ is fairly similar to
nm-connection-editor, with some simplification because we
currently only edit wireless connections.
The code in wireless-security/ is almost a straight copy
of the same code in nm-connection-editor, with some changes
to the .ui files to make them fit better in the new design.
When the user switches the hotspot switch off, we present a
confirmation dialog which can be canceled. We do keep the
hotspot running in that case, but we forget to set the switch
back to 'on'. Fix that.
gnome-shell relies on being able to call
gnome-control-center network connect-8021x-wifi <DEVICE> <AP>
This was broken in the big refactoring of the wifi panel
last cycle. Bring it back.
Instead of manually handling button release events on the
treeview, use activatable cell renderers for the ssid text
and for the arrow, and connect to activate signals for them.
We use cell area focus-sibling technology to make the keynav
in the list just have focus locations for the ssid and the
arrow.
This makes the details pages reachable by keynav, which was
not the case before.
The mode cell renderer had a property named 'mode', which
clashed with the GtkCellRenderer property of that name, which
confused the treeview keynav.
Rename the new property to ap-mode.
Remove the reference to the new longer existing viewport_list
widget, and be more careful about getting a NMRemoteSettings
object when calculating the last used time.
Showing it whenever we have a saved connection goes wrong for
all items where we have both an ap and a saved connection.
Also, use the same details page for out-of-range saved connections.
Copy the 'Last used' item for non-active, in-range access
points.
This is another step towards using the same details page
for all aps and connections.
When showing the details for an in-range, but not active access
point, we were just always showing details for the currently
active connection. This commit starts to sort things apart.
'Connect to hidden' is not really an access point.
Update the function name to reflect that. Also, update
the translator comment to be more to the point.
The code was assuming that 'editing' always means editing the
currently active connection. With the new design of the wifi
details tabs, that is no longer the case, we want to be able
to edit non-active connections. This commit makes it so.
