[zenity] Fix for Bug 567663. Now the --pulsate option works properly

[Arx Henrique Pereira da Cruz <arxcruz src gnome org>]

commit 1e88554c3f18c5b92a8a2724bf36d875eb6bd8f0
Author: Arx Cruz <arxcruz gnome org>
Date:   Thu Apr 19 16:10:21 2012 -0300

    Fix for Bug 567663. Now the --pulsate option works properly

 src/progress.c |   12 ++++++++----
 1 files changed, 8 insertions(+), 4 deletions(-)
---
diff --git a/src/progress.c b/src/progress.c
index b16e400..d17b359 100644
--- a/src/progress.c
+++ b/src/progress.c
@@ -92,10 +92,6 @@ zenity_progress_handle_stdin (GIOChannel   *channel,
 
     string = g_string_new (NULL);
 
-    if (progress_data->pulsate) {
-      zenity_progress_pulsate_start (progress_bar);
-    }
-
     while (channel->is_readable != TRUE)
       ;
     do {
@@ -221,6 +217,14 @@ zenity_progress_read_info (ZenityProgressData *progress_data)
   g_io_channel_set_encoding (channel, NULL, NULL);
   g_io_channel_set_flags (channel, G_IO_FLAG_NONBLOCK, NULL);
   g_io_add_watch (channel, G_IO_IN | G_IO_HUP, zenity_progress_handle_stdin, progress_data);
+  /* We need to check the pulsate state here, because, the g_io_add_watch
+     doesn't call the zenity_progress_handle_stdin function if there's no
+     input. This fix the Bug 567663 */
+  if (progress_data->pulsate) {
+      GObject *progress_bar = gtk_builder_get_object (builder, "zenity_progress_bar");
+      zenity_progress_pulsate_start (progress_bar);
+      g_object_unref(progress_bar);
+  }
 }
 
 void