[Bug 644776] Macro to check check mutability in set_property functions

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=644776

--- Comment #9 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Created attachment 339705
  --> https://bugzilla.gnome.org/attachment.cgi?id=339705&action=edit
elements: use new property mutability check macro

Seems to work, judging by the 'make check' carnage:

bin:test_state_change_skip: Trying to set property state-error on element
fakesink in READY state, but property is not marked as mutable in ready state.

gst/gstelement:test_property_notify_message: Trying to set property dump on
element identity0 in READY state, but property is not marked as mutable in
ready state.

identity:test_signal_handoffs: Trying to set property signal-handoffs on
element identity0 in PLAYING state, but property is not marked as mutable in
paused or playing state.

multiqueue:test_watermark_and_fill_level: Trying to set property low-watermark
on element multiqueue0 in PAUSED state, but property is not marked as mutable
in paused or playing state.
multiqueue:test_high_threshold_change: Trying to set property high-percent on
element multiqueue0 in PAUSED state, but property is not marked as mutable in
paused or playing state.
multiqueue:test_low_threshold_change: Trying to set property high-percent on
element multiqueue0 in PAUSED state, but property is not marked as mutable in
paused or playing state.

selector:test_output_selector_no_srcpad_negotiation: Trying to set property
pad-negotiation-mode on element outputselector0 in PLAYING state, but property
is not marked as mutable in paused or playing state.

tee:test_allow_not_linked: Trying to set property allow-not-linked on element
tee in PLAYING state, but property is not marked as mutable in paused or
playing state.

queue2: test_watermark_and_fill_level: Trying to set property low-watermark on
element queue2-0 in PAUSED state, but property is not marked as mutable in
paused or playing state.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.