From 60d1c3054aa60d02c763538d6b1f16d9d6ab6ade Mon Sep 17 00:00:00 2001 From: Matthew Barnes Date: Fri, 8 Feb 2013 14:21:42 -0500 Subject: G_PRIORITY_HIGH_IDLE is sufficient to beat GTK+ redraws. GTK+ uses (G_PRIORITY_HIGH_IDLE + 20) for redrawing operations, which is actually a slightly lower priority than G_PRIORITY_HIGH_IDLE. Therefore for our purpose, G_PRIORITY_HIGH_IDLE is sufficient. --- libemail-engine/e-mail-utils.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'libemail-engine/e-mail-utils.c') diff --git a/libemail-engine/e-mail-utils.c b/libemail-engine/e-mail-utils.c index e7f414a7d9..6614ecf67b 100644 --- a/libemail-engine/e-mail-utils.c +++ b/libemail-engine/e-mail-utils.c @@ -824,8 +824,10 @@ free_mail_cache_thread (gpointer user_data) e_cancellable_mutex_unlock (&photos_cache_lock); } - /* schedule with priority higher than gtk+ uses for animations (check docs for G_PRIORITY_HIGH_IDLE) */ - g_idle_add_full (G_PRIORITY_HIGH, free_mail_cache_idle, user_data, NULL); + /* Prioritize ahead of GTK+ redraws. */ + g_idle_add_full ( + G_PRIORITY_HIGH_IDLE, + free_mail_cache_idle, user_data, NULL); return NULL; } -- cgit