net connection should refresh scopes

i use networkinfo for help,get the current networkmode,and then get the accesspointname,when you connect to net and success, dashcontent will refresh all scopes

The attached fix for unity8 looks good and will most likely do what it's supposed to do, but I wonder if this is good strategy. What this change effectively means is: if scope is currently active (visible) while network becomes available, it will be refreshed; if it's not visible (but favorited), it will be marked "dirty" and refreshed when user swipes/selects it. To my understanding this will affect not only the after-boot scenario, but normal usage as well. What if network is flaky and goes offline/online a lot? We'll end up re-querying scopes more often than necessary, disregarding TTL of the results (currently visible results may still be "valid", but forcefully refreshed just because network gets available). Perhaps the shell should cooperate more closely with shell plugin with this, rather than forcing refresh?

Yes, thanks,maybe what i deal with it seems rude(dash will refresh only when device connect successfully). We don't always want to refresh some scopes when net connect. But i don't know when we need to refresh scopes or when we leave scopes alone, flaky network is also a question for this bug. (refreshing with a blank scope is a question needs to deal)

Honestly i think this should be done on the unity-scopes-plugin rather than on the unity-dash itself, the unity-scopes-plugin has more information about whether a network reconnect should end up in a refresh or not.