Blender Git Commits

adaptive_cloth: Mesh elements: get_self_index()

adaptive_cloth: AdaptiveMesh: set_edge_sizes()

Based on the `Sizing` stored in the `Vert`s of the `Edge`s, store the
"size" of the `Edge` in it's extra data.

adaptive_cloth: Mesh: change visibility of many utility functions

Make them protected instead of private.

Functions that get some element from the `Mesh` (maybe through other
elements) can be used by derived classes. It might make sense to make
these functions public directly instead of protected but will take
that decision later.

adaptive_cloth: Vert: get_uv() and get_uv_mut()

adaptive_cloth: Mesh: get extra data from elements

Simple functions to get extra data from elements.
It is possible make `extra_data` public but this reduces readability
of the code. By having these functions, intent is obvious.

adaptive_cloth: AdaptiveMesh: set and retrieve `Node`s extra data

From the `Cloth::verts`, set the extra data in the `Mesh::nodes`.

Delete the `Cloth::verts` to not have duplicate data.

Allocate data for `Cloth::verts`, and set from the `Mesh::nodes`.

adaptive_cloth: Mesh: get elements mutably

Useful to get the elements mutably.

This does make `Mesh` less "safe" since anyone can add or delete
elements without creating/deleting the necessary referencing between
the elements but this shouldn't be too much of a problem because it
would lead to an instant forced crash when the `Mesh` is used for
anything.

adaptive_cloth: BKE_cloth_remesh: convert to and from AdaptiveMesh

adaptive_cloth: Sizing: get edge size squared

adaptive_cloth: VertData: initial implementation

Used to store extra `Vert` data in the `Mesh`.

adaptive_cloth: NodeData: initial implementation

Used to store extra `Node` data in the `Mesh`.

adaptive_cloth: BKE_cloth_remesh() add to namespace blender::bke

bli: float2x2: multiply matrix with float

bli: float2x2: add 2 matrices

bli: float2x2: initial implementation

adaptive_cloth: Mesh: collapse edge: all v1 should point to n1

Sometimes, `n1` will have still have verts attached to it, so it makes
sense to make those verts point to `n2` but keep their UV coordinates
since attempting to merge verts not joined by edges can lead to lot of
issues. So essentially, extra `v1`s becomes `v2`s.

adaptive_cloth: fix: Mesh: split edge: reference is broken

The reference to the edge is broken because adding or deleting an edge
can realloc memory which means all the references are invalid. So just
need to recreate the references after a addition or deletion of an
element.

Would really appreciate a borrow checker to handle such
instances.

adaptive_cloth: Mesh: flip_edge: do operation by deleting and adding

Sometimes, the user needs to know which elements have been affected,
for this, delete and add new elements. This shouldn't have any effect
on performance in theory because the arena should add back the
elements in the place where it has been deleted, hasn't been tested.

adaptive_cloth: Mesh: is_edge_flippable(): works with across_seams

It is useful to know if the "3D edge" is flippable or not. This is
essentially done by going over all the `Edge` formed by the `Node`s of
the `Edge` and working with all those faces as a whole. Here we also
need to ensure that the edge is not on a seam. It actually might be
possible to optimize this and remove the boundary check entirely.

adaptive_cloth: Mesh: is_edge_on_boundary()

Checks if the given edge lies on the boundary of the mesh.