diff options
| author | Johannes Schmid <jhs@gnome.org> | 2009-11-18 10:38:45 +0100 |
|---|---|---|
| committer | Johannes Schmid <jhs@gnome.org> | 2009-11-18 10:38:45 +0100 |
| commit | bffd43bd8ff9761f263609583190314530706056 (patch) | |
| tree | 3fc7f2bc7b0c8239d1876db7922bf2283e91b511 /gtk/gtktoolitemgroup.c | |
| parent | 3cc1478a2951da5b3ba626d31747ab2d1dc96fea (diff) | |
| download | gtk+-bffd43bd8ff9761f263609583190314530706056.tar.gz | |
toolpalette: Don't call gdk_window_process_updates() in the animation callback
That does not seem to make any difference.
Diffstat (limited to 'gtk/gtktoolitemgroup.c')
| -rw-r--r-- | gtk/gtktoolitemgroup.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/gtk/gtktoolitemgroup.c b/gtk/gtktoolitemgroup.c index 838068f46d..92716f2ff8 100644 --- a/gtk/gtktoolitemgroup.c +++ b/gtk/gtktoolitemgroup.c @@ -1829,14 +1829,6 @@ gtk_tool_item_group_animation_cb (gpointer data) if (timestamp >= ANIMATION_DURATION) priv->animation_timeout = NULL; - /* Ensure that all composited windows and child windows are repainted, before - * the parent widget gets its expose-event. This is needed to avoid heavy - * rendering artifacts. GTK+ should take care about this issue by itself I - * guess, but currently it doesn't. Also I don't understand the parameters - * of this issue well enough yet, to file a bug report. - */ - gdk_window_process_updates (GTK_WIDGET (group)->window, TRUE); - retval = (priv->animation_timeout != NULL); GDK_THREADS_LEAVE(); |