On 04/25/2013 08:04 PM, Kip Warner wrote: > Hey Chris. Your message was not very useful again, but thanks anyways. > As you realized after, the problem may be too many graphical related > events through the main loop. I will try adjusting the animation's > framerate and seeing if I can get the worker thread to give a breather > to the main thread which seems to be working when using an idle_add() > callback to trigger an event flush.
As both Chris and Colomban have state, triggering an event flush isn't going to help. If the events are already getting filed up, trying to flush them isn't going to work. You have to figure out why the events are piling up. Because they're going to keep piling up no matter how often you try to pump the event loop. Something I do for animations is have a timeout callback that updates the GtkDrawingArea with the latest buffer, rather than updating the drawing area whenever something is drawn. Sounds like you're trying to re-invent the wheel here as well. From what you say (when you're not berating people for being unhelpful), you've implemented your own throbber widget. Perhaps you should either use a Gtk throbber, or study the throbber widget code and implement something along the same lines with your own graphic. _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
