Blender Git Loki

Cleanup: Don't use unsupported struct initialization

Although this worked for me, it appears this isn't supported until C++20.

Geometry Nodes: Use UI settings for properties in modifier

The system for exposing property settings like min, max, default, subtype,
etc. for ID properties is quite convoluted currently, so I won't give a
full description here, but this commit creates the tree of ID properties
needed to store that information. This means that property subtypes like
"angle" or "XYZ" will affect the display in the modifier.

Limitations:
- The _RNA_UI property is displayed in the modifier. This may require a
modification to uiDefAutoButsRNA to fix.
- IDProperties must have unique names, but node sockets don't have
that limitation. This can be solved by adding a "UI name" field to
IDProperties.

Fixup for cmake header cleanup

Issue introduced on f73a420e5aceb610bc38.

Geometry Nodes: Create the node group when adding a new Nodes modifier

Cleanup: Nodes Modifier header to its proper location

Geometry Nodes: do not reference custom data layers when copying mesh

We can't use that for now, because the original mesh might be freed
before the new copied mesh. When the original mesh is freed, the shared
layers will be freed as well.

This can probably be improved in the future, so that we can actually
share attribute arrays between meshes. An approach similar to how
geometries and components are shared should work as well.

Geometry Nodes: add comment mentioning that custom data might be shared

Geometry Nodes: refactor Geometry type

A geometry now contains zero or more geometry components.
A geometry component is a subclass off GeometryComponent.
Currently, there is a MeshComponent and PointCloudComponent.

A geometry contains at most one component of each type.
Individual components can be shared between multiple geometries
to avoid unnecessary copies. For that, each component has a user
count that determines when the component will be freed and whether
it is mutable.

Code working with geometries can either work with the components
directly, or use the utility functions on the geometry that cover the
most common operations.

In the future, additional component types can be added. For example,
we'll probably need components for curves and volumes.
Furthermore, something like an InstancesComponent can be added,
which contains points with attributes and references a geometry/object/collection
that is instanced on all the points.

Merge branch 'master' into geometry-nodes

Merge branch 'master' into geometry-nodes

Geometry Nodes: make default group output node active

Otherwise some updates were missing when sockets are changed.

Merge branch 'master' into geometry-nodes

Geometry Nodes: fix missing update when inserting a node between two nodes

Geometry Nodes: improve api for nodes

The execute callback of a geometry node gets more domain specific
types as parameters now: GeoNodeInputs and GeoNodeOutputs.

Those types are also aware of what node is being executed and can
provide better error messages when they are used incorrectly.

Merge branch 'master' into geometry-nodes

Merge branch 'master' into geometry-nodes

Merge branch 'master' into geometry-nodes

Merge branch 'master' into geometry-nodes

Geometry Nodes: Support pointcloud in transform node

This is likely not the final implementation of the transform node, but
it's a good trivial case for supporting multiple geometry data types.

Fix group input is resetting in modifier