Henry Wilkes 74ae0ba5df container: freeze notifies during add and remove ... Hold the notify signals for the container and the children until after the child has been fully added or removed. After the previous commit, this was used to ensure that the notify::priority signal was sent for children of a clip *after* the child-removed signal. This stopped being the case when the code in ->child_removed was moved to ->remove_child (the latter is called before the child-removed signal is emitted, whilst the former is called afterwards). Rather than undo this move of code, which was necessary to ensure that ->add_child was always reversed, the notify::priority signal is now simply delayed until after removing the child has completed. This was done for all notify signals, as well as in the add method, to ensure consistency. This allows the test_clips.py test_signal_order_when_removing_effect to pass. Also make subclasses take a copy of the list of the children before setting the start and duration, since this can potentially re-order the children (if they have the SET_SIMPLE flag set).		2020-03-16 14:19:52 +00:00
..
benchmarks	Remove autotools build system	2019-10-13 13:54:19 +01:00
check	container: freeze notifies during add and remove	2020-03-16 14:19:52 +00:00
validate	validate: Move to the new GstValidateEncodingTestInterface API	2019-11-20 18:07:22 -03:00
meson.build	meson: Build benchmarks	2019-03-15 16:18:58 -03:00