HI Lorn, just noting that scopes *generally receive the network connectivity status as an enum passed to them from the unity-scopes-shell as metadata. The only thing that scope-aggregator does with the network status is (depending on the scope config), it displays a "Hey, no network" type message. Beyond this, responding reasonably to no-network conditions is up to child scopes.
HI Lorn, just noting that scopes *generally receive the network connectivity status as an enum passed to them from the unity-scopes-shell as metadata. The only thing that scope-aggregator does with the network status is (depending on the scope config), it displays a "Hey, no network" type message. Beyond this, responding reasonably to no-network conditions is up to child scopes.
Not sure it is relevant, but I have found an issue with this enum: https:/ /bugs.launchpad .net/ubuntu/ +source/ unity-scopes- api/+bug/ 1502282/ comments/ 24
* I say "generally" because scopes *can* take additional steps.