GNOME Bugzilla – Bug 555898
[optimisation] Block signals from timeline while doing complex changes
Last modified: 2009-05-07 17:15:31 UTC
+++ This bug was initially created as a clone of Bug #396803 +++ When doing a SimpleTimeline move, several sources are being moved around, priorities changed, etc.... Currently, whenever a single property changes, the UI is updated, which is very cpu intensive. There should be a way to block all signal emissions from gnonlin to be forwarded from pitivi.timeline to the UI, and a way to then emit all those signals at once. This should be done in gnlcomposition. One idea is to have a boolean 'block-updates' on gnlcomposition, which, when activated takes into accounts the modifications of the contained objects but doesn't actually do an internal pipeline update. When set back to False, it would see if it has a pending update and does it then.
commit d6e84eafc8b22c05d3da8849a4cdf46045a58f78 Author: Edward Hervey <bilboed@bilboed.com> Date: Wed May 6 16:21:01 2009 +0200 gnlcomposition: Implement update-blocking. Fixes #555898 When update is set to False, the internal pipeline is never updated, nor are the stop/duration properties of the composition. This allows for massive modifications with a much lower overhead.