[Bug 693281] [PATCH] GstObject: re-enable "notify::parent"

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=693281
  GStreamer | gstreamer (core) | git

Stefan Sauer (gstreamer, gtkdoc dev) <ensonic> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #4 from Stefan Sauer (gstreamer, gtkdoc dev) <ensonic at sonicpulse.de> 2013-02-07 06:35:46 UTC ---
A song in buzztard might not be fully connected at all times. The UI gives a
visual clue which elements are active (connected to the sink) by shading them.
The engine in buzztard is keeping a track of the graph of the song and the
graph in gstreamer. Whenever components are linked/unlinked, subgraphs might
get connected/disconneted on the gstreamer side. As a consequece the engine add
new connected parts to the running pipeline and removes disconnected parts from
it. The UI components simply watch the parent state to know if a component is
in the running pipeline or not.

If we can find a acceptable solution, I can always add such a signal on the
buzztard api level.

Regarding the gstreamer part - alternatves would be a recursive mutex, or
caching the list of parents.
Blocking signal handlers is not enough (as the signal emission is not he issue,
but the traversal of the parent hierarchy).

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.