summaryrefslogtreecommitdiff
path: root/libpurple/accounts.c
diff options
context:
space:
mode:
authorGary Kramlich <grim@reaperworld.com>2022-11-04 23:58:18 -0500
committerGary Kramlich <grim@reaperworld.com>2022-11-04 23:58:18 -0500
commitece630e3b63ac55f7d5b5582c259c5865f55eff0 (patch)
tree79771a0510ca672b033ea96fa49a3087ae0ca3fe /libpurple/accounts.c
parentd56ca463f4e91163af4d81dc208d180f376b6ad4 (diff)
downloadpidgin-ece630e3b63ac55f7d5b5582c259c5865f55eff0.tar.gz
Propagate the PurpleAccount::notify signal via PurpleAccountManager::account-changed
This new signal supports details and works just like notify does on the account instances, but it will be emitted for any account that the manager instance knows about which means we can remove the old purple signals. Testing Done: Enabled and disabled accounts in Pidgin via the menus to make sure things were working right, and verified via the console that the accounts were being enabled and disabled. Ran Finch, but I ran into the infinite loop bug in the buddy list clean when disabling an account which is a known issue. Reviewed at https://reviews.imfreedom.org/r/2032/
Diffstat (limited to 'libpurple/accounts.c')
-rw-r--r--libpurple/accounts.c8
1 files changed, 0 insertions, 8 deletions
diff --git a/libpurple/accounts.c b/libpurple/accounts.c
index 09a0c203f8..2cd2844ce9 100644
--- a/libpurple/accounts.c
+++ b/libpurple/accounts.c
@@ -680,14 +680,6 @@ purple_accounts_init(void)
void *handle = purple_accounts_get_handle();
void *conn_handle = purple_connections_get_handle();
- purple_signal_register(handle, "account-disabled",
- purple_marshal_VOID__POINTER, G_TYPE_NONE, 1,
- PURPLE_TYPE_ACCOUNT);
-
- purple_signal_register(handle, "account-enabled",
- purple_marshal_VOID__POINTER, G_TYPE_NONE, 1,
- PURPLE_TYPE_ACCOUNT);
-
purple_signal_register(handle, "account-created",
purple_marshal_VOID__POINTER, G_TYPE_NONE, 1,
PURPLE_TYPE_ACCOUNT);