GitLab

It gets modified during the life of the object. Fixes build.

From 2a59016 to c463bc0

This is now bindings firendly as _new is just a classic c convenience and all
the work is done in a constructor. As a side effect _new never fails.
Fix the tests.

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

int and int64 ranges can now have an optional step (defaulting to 1).
Members of the range are those values within the min and max bounds
which are a multiple of this step.

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

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

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

Make controlbinding an abstract baseclass. Move implementation to control-
binding-direct and add a control-binding-argb. Add an example.

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

We introduced our own when GLib didn't want to add a GType
for GError. But now that there is one, we can use GLib's
unconditionally and remove our version.

So pygi finds/uses the local g-i files.

Change _set_control_binding to _add_control_binding and take ownership. Add a
_remove_control_binding function.

This is needed to support multiple kinds of control-bindings.

If the getcaps functions returns NULL, return FALSE from the CAPS query.

It's reasonable to build from git, but not want to turn all compiler
warnings into fatal errors.  For example, GNOME's jhbuild helps people
get newer versions of software than came from their distribution, but
they may not necessarily want to hack on it.

Make the memory object simply manage the data pointer and the maxsize and move
the offset and size handling to common functionality.
Use the READONLY flag to set a readonly lock.
Remove the data and size fields from the unmap method. We need an explicit
resize operation instead of using the unmap function.
Make internal helper lock and unlock functions.
Update unit test and users of the old API.

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

From 0807187 to 2a59016

And only forward the allocation query if we're working in
passthrough mode if no ::propose_allocation is implemented.
In place buffer transformations will change the buffer
content and require explicit handling of all metas.

This has to be handled explicitely by elements to
make sure that they support all the metas passed
in the allocation query.
Metas have to supported explicitely, otherwise the
query will fail. All elements in a chain need to
support a specific meta to allow its usage.

Which should be soon, since we already depend on an unstable glib for -base.

It should work everywhere now, and -base and -good depend on
the GstNetMeta API.