On fre, 2013-02-15 at 22:48 -0500, Owen Taylor wrote: > On Fri, 2013-02-15 at 09:21 +0100, Alexander Larsson wrote: > > > > In terms of using timeBeginPeriod() and timeEndPeriod(), unfortunately, > > > the GDK level API has no concept of a "running animation", so it's not > > > clear when GDK would set up a period. We could add such a thing - > > > basically gdk_frame_clock_begin_continual_updates() - which would help > > > for style animations and gtk_widget_add_tick_count(). It wouldn't help > > > if a higher level built on top of GTK+ has an interface like > > > window.requestAnimationFrame() or we're reacting to mouse events. > > > > We could add such an api though. For instance, we could have a > > refcounted api on the paint clock like gdk_paint_clock_use/unuse() such > > that any running animations would cause a clock use and thus higher > > timing resolution on win32. > > I tried creating such an API - patch at: > > https://bugzilla.gnome.org/show_bug.cgi?id=693934 > > It's a reasonable addition, and in some ways an improvement, though it > makes the API a bit less minimal.
This seems reasonable to me. I added some win32 support patches and timeBeginPeriod support to the bug. _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
