Blender Git Loki

Update debug flag add date

GPencil: Fix bezier stroke selection

GPencil: Remove printf

Cycles: Remove unused draw() return value

Should be no functional changes since the return value was never used.

Minor cleanup

Merge branch 'master' into temp-lineart-contained

Merge branch 'master' into temp-gpencil-io

Construct-on-first-use to stay far away from static init. fiasco

We didn't actually run into the static initialization fiasco, but only
because `blender::Map` didn't use the guarded allocator on default
destruction. Better to stay far way from static initialization fiasco,
and the construct on first use idiom is trivial and prevents it. So
better use that.

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

GPencil: Revert changes in modifiers

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

Implement quality setting based on UI slider