[Gstreamer-bugs] [Bug 100563] Changed - object lifecycle is unclear/buggy

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=100563

Changed by david at neongoat.com.

--- shadow/100563	Sat Dec  7 13:47:17 2002
+++ shadow/100563.tmp.15883	Mon Dec 30 19:32:06 2002
@@ -1,12 +1,12 @@
 Bug#: 100563
 Product: GStreamer
 Version: 0.4.2
 OS: Linux
 OS Details: debian
-Status: NEEDINFO   
+Status: CLOSED   
 Resolution: 
 Severity: normal
 Priority: Normal
 Component: gstreamer (core)
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
 ReportedBy: david at neongoat.com               
@@ -42,6 +42,20 @@
 a) give the error you get
 b) provide a bt if it's a segfault
 c) attach a --gst-mask=-1 log
 
 as for the code itself, not sure why you want to do it like that.  A
 gst_object_unref (bin) would probably do all you want there.
+
+------- Additional Comments From david at neongoat.com  2002-12-30 19:32 -------
+The reason why I needed to do this is because my pipelines change
+dynamically and single elements are added/destroyed frequently without
+destroying or otherwise modifying the rest of the pipeline.
+
+wtay cleared up the lifecycle concepts one day on IRC, so I now know
+that calling gst_bin_remove() automatically destroys the removed
+element (unless the application manually reparents it). Before I was
+trying to manually destroy the elements. Since I wasn't familiar with
+the gtk lifecycle I didn't nkow that's how it works in gst.
+
+If necessary, I can help out with the docs, including info like this
+that someone with no gst experience would need.