Blender Git Commits

LineArt: data copying and mofifier UI for vgroup.

LineArt: Vertex group data structure changes.

LineArt: GPencil modifier API changes.

Merge remote-tracking branch 'origin/master' into lanpr-under-gp

Merge remote-tracking branch 'origin/master' into lanpr-under-gp

# Conflicts:
# source/blender/python/mathutils/mathutils_Matrix.c

Fix T81100: ccl::Node: ASan SEGV due to bad pointer

`SOCKET_OFFSETOF` was added in the initial commit {rBec51175f1fd6c91d5}
when `offsetof` [1] was not supported well enough. GCC and LLVM
support it since C++17.

Other two changes: type and size check can be done without creating
an invalid address too.

[1] https://cppreference.com/w/cpp/types/offsetof

Reviewed By: campbellbarton, brecht

Maniphest Tasks: T81100

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

Cleanup: use angle-brackets for email addresses

This is already the most widely used convention.

Use this so `make check_spelling_c` will ignore all email addresses.

API Docs: Correct syntax for bpy.utils.register_class

UI: Motion Tracking: Fix description of K2 coefficient

Fixed description of K2 coefficient. It is second coefficient

Reviewed By: Blendify

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

Cleanup: sort cmake file lists

Cleanup: sort struct declarations

API docs: Fix sytax error for delaunay_2d_cd

Alternative solution to https://developer.blender.org/D8546

Cleanup: remove full-stop from description

UI: Remove second person in warning message

This phrasing can feel like an accusation, and a simpler phrase
gets across the idea just as well.

Fix unreported Eisenbug leading to a crash when reading a blend file.

This took more than a day to fully investigate and understand, one of
the reasons being that the probability of the issue to show up was
extremely low, and subjected to very specific random factors.

Root of the issue is that, in some very rare cases, a newly read ID
might get the exact same memory address as the one it had when the blend
file was saved.

In that case, `BKE_workspace_active_set` would return immediately, since
the pointer to the active workspace would remain unchanged. But that
lead to having an unset NULL active layout pointer, which would crash
when attempting to get e.g. the active screen.

For the record, I ran into this when running a specific build (master
with one flag added to the `LIB_ID_CREATE` ones, with value `1 << 3`),
using a specific set of options (`--background --factory-startup -noaudio`),
and passing the .blend file from T80090 as argument.

Cleanup: spelling

Cleanup: Use LISTBASE_FOREACH macro in outliner code

Fix use after free deleting object with modifier panels visible

It's necessary to check if the panels are active before accessing their
data. Thanks to @ankitm for reporting this.

API Docs: Fix corrupted document of gpu.select.load_id

The Python API document of gpu.select.load_id does not follow rst format.
c.f. https://docs.blender.org/api/current/gpu.select.html

This patch fixes it.

Reviewed By: Blendify

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

Sculpt: Preserve Mesh visibility from edit mode using the Face Sets

Before this change, when users switch from edit mode to sculpt mode, the
entire mesh would be visible. Even if in the edit mesh mode part of it was
set to invisible.

With this change the visibility is preserved, by creating a separate face set
for the visible and invisible parts of the mesh and setting their initial visibility.

Implementation details: This adds a function to initialize a new Face Set
datalayer taking the current mesh visibility into account which is stored
in the ME_HIDE flag of the vertices.

Reviewed By: sergey

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