State changes to GST_STATE_NULL not being communicated.

[Yogesh Marwaha]

On Tuesday 02 Apr 2013 09:41:32 Xabier Rodriguez Calvar wrote:
> O Lun, 01-04-2013 ás 17:39 +0100, Tim-Philipp Müller escribiu:
> > This is expected behaviour (both in 0.10 and 1.0).
> > 
> > You can disable that behaviour via GstPipeline API
> > (auto-flush-bus=false), but then you'll always have to make sure to
> > pop
> > all pending messages off the bus yourself.
> 
> I think you can also check the returned value of gst_element_set_state
> and consider it committed when returning GST_STATE_CHANGE_SUCCESS. That
> could be easier than handling the messages flushing yourself.
> 
> Best regards.

Hmm. How I missed that! Can I trust the documentation of 
gst_element_set_state() which read as follows: -
"State changes to GST_STATE_READY or GST_STATE_NULL never return 
GST_STATE_CHANGE_ASYNC."

If this is the case, it either return success or failure. I am happy with that 
:-0

Thank you both,

Regards,

Yogesh