comparison libpurple/log.c @ 18093:c0a09c56d0c5

Custom logger selection doesn't work after a restart. To fix this, we do a check whenever a new logger is added, and start using it if this is what the user really wants. This commit message is longer than the actual patch.
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Wed, 13 Jun 2007 12:26:48 +0000
parents 9018b785ef73
children 873ee0038752
comparison
equal deleted inserted replaced
18092:662564beb575 18093:c0a09c56d0c5
404 { 404 {
405 g_return_if_fail(logger); 405 g_return_if_fail(logger);
406 if (g_slist_find(loggers, logger)) 406 if (g_slist_find(loggers, logger))
407 return; 407 return;
408 loggers = g_slist_append(loggers, logger); 408 loggers = g_slist_append(loggers, logger);
409 if (strcmp(purple_prefs_get_string("/purple/logging/format"), logger->id) == 0) {
410 purple_prefs_trigger_callback("/purple/logging/format");
411 }
409 } 412 }
410 413
411 void purple_log_logger_remove (PurpleLogLogger *logger) 414 void purple_log_logger_remove (PurpleLogLogger *logger)
412 { 415 {
413 g_return_if_fail(logger); 416 g_return_if_fail(logger);