[gstreamer-bugs] [Bug 555898] New: [optimisation] Block signals from timeline while doing complex changes

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=555898

  GStreamer | gnonlin | Ver: HEAD CVS
           Summary: [optimisation] Block signals from timeline while doing
                    complex changes
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gnonlin
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bilboed at gmail.com
         QAContact: bilboed at gmail.com
OtherBugsDependingO 396803
             nThis:
     GNOME version: Unspecified
   GNOME milestone: Unspecified


+++ 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.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=555898.