Blender Git Loki

LibOverride: Resync: Fix most remaining 'overrides in master collection' issues.

Problem is, when a collection is excluded from the scene, none of its
objects are technically instantiated.

This should not happen when *creating* an override, but can be fairly
common during resync process.

For now, use a lesser precise check in resync case, only relying on
object usercount. This might lead to some objects being left without any
collection in some rare weird case, but this cannot really be avoided
currently.

LibOverride: Resync: Fix too many objects being rooted in master collection.

No need to instantiate systematically the root object if it is already
instantiated in the scene...

Issue reported by the studio.

LibOverride: tweak log messages, fix crash in log code.

One of the log call could use freed memory.

Python GPU: Improve the Python GPU API documentation

This fixes some errors of continuity and consistency of formatting on
https://docs.blender.org/api/current/gpu.html

This also details the description of some parameters.

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

Merge branch 'ui-asset-view-template' into asset-browser-poselib

Fix asset storage crash when closing Blender in release mode

support default weight

GPencil: Remove Curve runtime data

WIP: This commit produces compiler errors

Tweak the collection propery tab location

Use custom .py property for active asset index, stored in the workspace

Previously I just used the active color index of the first palette to
get things to work.
I would've preferred if the asset view template could register own
properties and store them in the `UIList` it creates. That way you could
have multiple asset views with entirely independent data. But since this
isn't possible, we need a different way to store such data, I think the
workspace makes sense. It should still be possible to store different
data for different use-cases, e.g. to show a pose asset list in pose
mode and a material asset list in object mode. So idea is to let
scripts/add-ons register custom properties for their specific use case
(e.g. "Active Pose Asset" for the pose libraries).

Use custom .py property for active asset index, stored in the workspace

Previously I just used the active color index of the first palette to
get things to work.
I would've preferred if the asset view template could register own
properties and store them in the `UIList` it creates. That way you could
have multiple asset views with entirely independent data. But since this
isn't possible, we need a different way to store such data, I think the
workspace makes sense. It should still be possible to store different
data for different use-cases, e.g. to show a pose asset list in pose
mode and a material asset list in object mode. So idea is to let
scripts/add-ons register custom properties for their specific use case
(e.g. "Active Pose Asset" for the pose libraries).

GPencil: Check Stroke type using Evaluated data

GPencil: Remove Bezier curve data in Evaluated strokes

As we have no time to implement Beziers in modifers, we remove in the eval data the curve to keep all system running.

Merge fix from D10363

Fix T86612 EEVEE: Wrong AmbientOcclusion on refractive materials

This is because the refractive materials were using the deferred AO
computation instead of tracing their own.

GPencil: Revert changes in modifiers

We undo all changes and keep only polygon type code. The Bezier type will be implement in the future.

Cleanup: NULL -> nullptr.

Cleanup: replace std::map with blender::Map.

Cleanup: Replace std::vector with blender::Vector.

Cleanup: Modernize iterators.