mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-22 08:50:38 +01:00
f0731dc716
The flags allow for more then two reasons. Currently the only reasons
for allowing or disallowing autoconnect are "user" and "intern".
It's a bit odd, that NMDeviceAutoconnectBlockedFlags has a negative
meaning. So
nm_device_set_autoconnect_intern (device, FALSE);
gets replaced by
nm_device_set_autoconnect_blocked_set (device, NM_DEVICE_AUTOCONNECT_BLOCKED_INTERN);
and so on.
However, it's chosen this way, because autoconnect shall be allowed,
unless any blocked-reason is set. That is, to check whether autoconnect
is allowed, we do
if (!nm_device_get_autoconnect_blocked (device, NM_DEVICE_AUTOCONNECT_BLOCKED_ALL))
The alternative check would be
if (nm_device_get_autoconnect_allowed (device, NM_DEVICE_AUTOCONNECT_ALLOWED_ALL) == NM_DEVICE_AUTOCONNECT_ALLOWED_ALL)
which seems odd too.
So, add the inverse flags to block autoconnect.
Beside refactoring and inverting the meaning of the autoconnect
settings, there is no change in behavior.
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| nm-bluez-common.h | ||
| nm-bluez-device.c | ||
| nm-bluez-device.h | ||
| nm-bluez-manager.c | ||
| nm-bluez4-adapter.c | ||
| nm-bluez4-adapter.h | ||
| nm-bluez4-manager.c | ||
| nm-bluez4-manager.h | ||
| nm-bluez5-dun.c | ||
| nm-bluez5-dun.h | ||
| nm-bluez5-manager.c | ||
| nm-bluez5-manager.h | ||
| nm-bt-error.c | ||
| nm-bt-error.h | ||
| nm-device-bt.c | ||
| nm-device-bt.h | ||