On Sun, 2009-01-18 at 21:31 +0000, Emmanuele Bassi wrote: > let me see if I understand what you're trying to achieve: you want to be > able to make Clutter's redraw cycle depend on another set of conditions > -- basically, "slaving" Clutter's redraw to another redraw cycle.
What I'm trying to do can perhaps be more generally expressed this way, yes. > for that, Clutter 1.0 will have the ::queue-redraw signal on the > ClutterStage: you connect to the signal (which is invoked when something > queues a redraw on a ClutterStage), block it, queue a redraw on your > redraw cycle and then let that cycle call clutter_redraw(). This sounds very much like it would do the trick, and certainly much cleaner than adding idle handlers with the appropriate priorities to get called before and after the redraw. > this won't be backported to the current stable cycle, though. I'm using 0.9 from git at the moment. When will ::queue-redraw land? Thanks, Jason. -- To unsubscribe send a mail to [email protected]
