- 06 Jul, 2020 4 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- 03 Jul, 2020 2 commits
-
-
Sebastian Dröge authored
Fixes #268
-
Sebastian Dröge authored
Fixes #273
-
- 02 Jul, 2020 1 commit
-
-
François Laignel authored
-
- 30 Jun, 2020 8 commits
-
-
Sebastian Dröge authored
Otherwise we would post a message, which calls into this code again and then does the whole thing recursively forever.
-
Sebastian Dröge authored
It regularly fails in normal situations, e.g. when the element is not inside a bin and has no bus, and we don't really want to log errors for that.
-
Sebastian Dröge authored
This is more in line with the C API and simplifies callers in Rust.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
They were side-stepping the miniobject writability mechanism.
-
Sebastian Dröge authored
Those are automatically provided already.
-
Sebastian Dröge authored
gobject-introspection does not support this yet so we have to do that manually. Fixes #271
-
Sebastian Dröge authored
And instead directly implementing this via the macro on the target types.
-
- 25 Jun, 2020 5 commits
-
-
Sebastian Dröge authored
And also make the video event API more consistent with the normal event API. Fixes #269
-
François Laignel authored
See !532 (comment 548884)
-
François Laignel authored
... and deprecate the `Query::new_*` forms.
-
François Laignel authored
... and deprecate the `Event::new_*` forms.
-
François Laignel authored
... and deprecate the `Message::new_*` forms.
-
- 22 Jun, 2020 4 commits
-
-
-
Sebastian Dröge authored
Instead of taking a new reference to the pad.
-
Sebastian Dröge authored
Sounds more natural as it creates a build that is initialized *with* a template. But keep Pad::from_template() as it creates a new pad *from* a template.
-
Sebastian Dröge authored
This handles safely setting the pad functions during construction and also has special support for ghost pads. Fixes #247
-
- 21 Jun, 2020 4 commits
-
-
Sebastian Dröge authored
That's generally not a good idea and not safe to do.
-
Sebastian Dröge authored
It's generally not safe to change the object name after construction and not really a good idea.
-
Sebastian Dröge authored
This is not thread-safe and changing the function at a bad time will cause crashes or worse. It's only really safe to set the functions right after construction of the pad before any other code can know about it. Fixes #247
-
Sebastian Dröge authored
No need to provide the field name if it's initialized with a variable of the same name.
-
- 19 Jun, 2020 2 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- 18 Jun, 2020 1 commit
-
-
Sebastian Dröge authored
-
- 16 Jun, 2020 1 commit
-
-
Sebastian Dröge authored
-
- 11 Jun, 2020 2 commits
-
-
Guillaume Desmottes authored
The idiomatic way for Rust constructors is to be named from_XXX() instead of new_from_XXX() and with_XXX() instead of new_with_XXX(). Fix #460
-
Guillaume Desmottes authored
-
- 09 Jun, 2020 1 commit
-
-
Guillaume Desmottes authored
Use re-export pattern from glib. Fix #255
-
- 08 Jun, 2020 1 commit
-
-
Sebastian Dröge authored
-
- 04 Jun, 2020 1 commit
-
-
Sebastian Dröge authored
Static variables in generic functions only exist once and not once per type parameter, so before we were only able to register exactly one filter type.
-
- 03 Jun, 2020 1 commit
-
-
- 02 Jun, 2020 1 commit
-
-
Sebastian Dröge authored
-
- 01 Jun, 2020 1 commit
-
-
Including most debugging related functions. Fixes #211
-