Dan Williams 14537c71d8 libnm-core: emit added/removed signals before property change notifications ... Because internal objects do some processing/setup in the various _added class signal handlers, they need to be emitted before property change notifications. Otherwise it leads to situations where external objects that listen to NMClient property changes will be called before internal processing has been completed. Specifically, NMRemoteSettings uses connection_added() to check connection visibility and assign the new connection to one of two internal arrays. If a client got a property notification for NMClient::connections before NMRemoteSettings can process the new connection, then nm_client_get_connections() will return an empty array because NMRemoteSettings hasn't had the chance to add the new connection to priv->visible yet, which is done in NMRemoteSettings::connection_added(). Fixes:Beaker:NetworkManager_Test240_nmtui_general_realtime_refresh_edit_screen		2014-11-07 16:58:43 -06:00
..
common.c	libnm: abstract out duplicated device-creating code in tests	2014-10-19 09:27:47 -04:00
common.h	libnm: abstract out duplicated device-creating code in tests	2014-10-19 09:27:47 -04:00
libnm-test-launch.sh	tests: Don't run session-long dbus daemons for tests	2014-10-24 19:16:33 +02:00
Makefile.am	libnm: port to GDBus	2014-09-18 11:51:09 -04:00
test-nm-client.c	libnm-core: emit added/removed signals before property change notifications	2014-11-07 16:58:43 -06:00
test-remote-settings-client.c	libnm: change GSList to GPtrArray in libnm methods	2014-10-28 17:17:17 -04:00
test-secret-agent.c	libnm-core, libnm, settings: move NMSecretAgentError to nm-errors	2014-10-22 08:29:09 -04:00