Blender Git Loki

Merge branch 'master' into greasepencil-object

synchronize with addons

Merge branch 'master' into greasepencil-object

Oculus Touch controllers support: all inputs exposed in python.

World transformation for navigation, exposed in python.
Fix: frustum culling for asymetric frustums.

Merge branch 'master' into greasepencil-object

Merge branch 'master' into greasepencil-object

Update RNA Manual References

Merge branch 'master' into greasepencil-object

Merge branch 'master' into greasepencil-object

Merge branch 'master' into greasepencil-object

GPencil: Rename Percentage Mode

GPencil: Cleanup code

GPencil: New Percentage parameter in Build modifier

Add a factor to determine the percentage affected.

Still wip.

Merge branch 'master' into greasepencil-object

Two small fixes in interface_panel, slightly increase margin

Update for naming changes in master, various small changes

Merge branch 'panel-list-patch' into panel-list-patch-2

Merge branch 'master' into panel-list-patch

Alembic: export object data with object data name

The old exporter always exported a mesh object to `{object.name}/{object.name}Shape`. Now it exports to `{object.name}/{mesh.name}` instead. The same change also applies to other object data types.

Note that the code now is a bit hackish, as `m_name` is set even in cases where it isn't used. This hackishness was already there, though, but it's now just more visible. This will all be cleaned up when the Alembic exporter is ported to use the `AbstractHierarchyImporter` structure of USD.

Differential Revision: https://developer.blender.org/D7672

IO: ensure export path and export name are always consistent

Before this, there was one code path that set `context.export_path`,
and a different code path for `context.export_name`, allowing the two to
diverge.

Keeping track of the export path of the export parent (which can be but is
not always the Blender parent object) also allows a concrete subclass of
`AbstractHierarchyIterator` to find the `AbstractWriter` for the export
parent. In case of exporting to Alembic this is important, as it's not
possible to simply give the Alembic library the full export path of an
object (it needs the C++ object of the parent).