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. --- shell/e-shell-searchbar.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'shell/e-shell-searchbar.c') diff --git a/shell/e-shell-searchbar.c b/shell/e-shell-searchbar.c index 107a30a692..262b082d6c 100644 --- a/shell/e-shell-searchbar.c +++ b/shell/e-shell-searchbar.c @@ -1733,10 +1733,14 @@ e_shell_searchbar_load_state (EShellSearchbar *searchbar) gtk_action_unblock_activate (action); /* Execute the search when we have time. */ + g_object_ref (shell_view); searchbar->priv->state_dirty = FALSE; - /* schedule with priority higher than gtk+ uses for animations (check docs for G_PRIORITY_HIGH_IDLE) */ - g_idle_add_full (G_PRIORITY_DEFAULT, idle_execute_search, shell_view, NULL); + + /* Prioritize ahead of GTK+ redraws. */ + g_idle_add_full ( + G_PRIORITY_HIGH_IDLE, + idle_execute_search, shell_view, NULL); } void -- cgit v1.2.3