diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2021-05-23 21:17:42 +0200 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2021-05-26 13:14:52 +0000 |
| commit | e4f7da5624dc1dfc20373bf77bfc4f3309bacb61 (patch) | |
| tree | a6ce28e428eef7f35d0b419fe4225fda58b51328 /src/mm-base-bearer.h | |
| parent | 8cfc2a237af78734b4e4f1d7d89f4782dacf9bcd (diff) | |
base-bearer: propagate the new connection status after reload
Just triggering a connection status reload won't change the actual
bearer object state.
We change the signature of the reload_connection_status_finish()
method so that it returns the actual reloaded bearer connection
status, and so both the load_ and reload_ methods can be implemented
with exactly the same method, something that was not possible before.
Once we get the new connection status reloaded, we apply it in the
bearer object only if it's DISCONNECTED (and it wasn't DISCONNECTED
before). This should cover the true real case we're interested in, and
nothing else (i.e. we won't overcomplicate the logic attempting to
handle disconnected->connected transitions detected in the sync()
operation).
Diffstat (limited to 'src/mm-base-bearer.h')
| -rw-r--r-- | src/mm-base-bearer.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/mm-base-bearer.h b/src/mm-base-bearer.h index a02036ca..993abaa4 100644 --- a/src/mm-base-bearer.h +++ b/src/mm-base-bearer.h @@ -157,9 +157,9 @@ struct _MMBaseBearerClass { void (* reload_connection_status) (MMBaseBearer *bearer, GAsyncReadyCallback callback, gpointer user_data); - gboolean (* reload_connection_status_finish) (MMBaseBearer *bearer, - GAsyncResult *res, - GError **error); + MMBearerConnectionStatus (* reload_connection_status_finish) (MMBaseBearer *bearer, + GAsyncResult *res, + GError **error); #endif |