Blender Git Commits

LineArt: Occlusion effectiveness in material.

Cleanup: compiler warnings

Revert "Fix crash running constraint, modifier, fx from missing NULL check"

This reverts commit f4d5a69cf8512aafcc697d1b09f65489015b6af4.

This causes bpy.ops.object.modifier_apply.poll() to fail as
well as modifier binding operators (breaking tests).

BLI: support removing Map elements during iteration

While it was technically safe to call Map.remove while iterating over
a map, it wasn't really designed to work. Also it wasn't very efficient,
because to remove the element, the map would have to search it
again. Now it is possible to remove an element given an iterator
into the map. It is safe to remove the element while iterating over
the map. Obviously, the removed element must not be accessed
anymore after it has been removed.

BLI: add a common base class for Map iterators

This is useful for an upcoming commit that allows removing
an element based on an iterator.

Cleanup: Rename `#if GPU_USE_PY_REFERENCES` to `#ifndef GPU_NO_USE_PY_REFERENCES`

This is safer for incremental build.

And there was already a macro `GPU_USE_PY_REFERENCES` used elsewhere.

Fix accidental lines removed in the last commit

Fix gross errors in previous commit

Documentation: Replace the bgl API in the gpu module exemples

Python GPU: Add new methods to port the code templates in the manual

This commit adds a new API tha allow to replace the bgl API in the exemples on:
https://docs.blender.org/api/current/gpu.html

**Overview (New API):**
```
gpu.state: active_framebuffer_get
GPUFramebuffer: read_color
GPUOffscreen: texture_color
```

Reviewed By: brecht

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

Python GPU: Add reference of PyObject GPU object to the GPU object itself

Instead of creating different python wrappers for the same GPU object,
return the same `PyObject` created earlier.

This also allows for more secure access to existing GPU objects.

Reviewed By: brecht

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

Fix/Workaround T87511: snap gizmo flickers on Ctrl-Drag

Hack to bypass drag events, eventually the gizmo API
should support this use case without hacks.

Fix T85470: Simple deform modifier causes artifacts at low angles

The formula used to compute the bend did subtraction of two big numbers
to get the position. Changed to find the delta and add that,
by rearranging the formula into a more numerically stable form.

Reviewed By: mano-wii, campbellbarton

Ref D11074

Object: improve on fix for Object.to_mesh() crash T86871

While fa7ddd0f43ea15dd19d81e7808de2bfe8cfc89ee fixed the reported issue,
the possibility of reusing runtime data during curve-to-mesh conversion
remained. Instead of treating the bounding-box as a special case,
clear all run-time data for temporary objects.

Ref D11026

Reviewed By: sergey

BLI: improve VectorSet data structure

This adds two new methods:
* `clear` just removes all keys from the vector set.
* `index_of_or_add` returns the index of a key and adds it if has not
been added before.

Fix all objects getting selected sometimes when droppping object

If no other object was selected while dragging one in (e.g. from the Outliner
or an object asset from the Asset Browser), all visible objects in the active
view layer would get selected.
Issue was caused by a wrong enum type use.

Mistake in bcdba7c34da0.

Fix crash running constraint, modifier, fx from missing NULL check

None of these generic poll functions had NULL pointer checks,
since all operators that use these functions expect a valid constraint,
modifier .. etc. Add the NULL check to the poll function.

Ref D11126

Reviewed By: mont29, Severin

Fix: missing return

Object: rename BKE_object_runtime_free, leave data cleared

Rename BKE_object_runtime_free -> BKE_object_runtime_free_data,
since the runtime pointer is part of the object, only the data is freed.

Leave the data cleared to avoid accidental use,
this is in keeping with other `*_free_data()` functions.

Geometry Nodes: Add an "Auto" option for Attribute Convert data type

Currently there is an "Auto" option for the domain, this commit adds a
similar option for "Auto" data type, that uses the data type from the
target attribute or the source attribute (in that order).

Ref T87347

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