Blender Git Commits

Cleanup: pose lib, clarify comment

Merge remote-tracking branch 'origin/master' into asset-browser-poselib

# Conflicts:
# source/blender/blenloader/intern/versioning_290.c

Use custom collection property to pass the asset list to UI lists

`UIList` is designed to use collection properties. I previously did a
whole bunch of hacks to use it without. This isn't acceptable for
master, instead a proper collection property should be provided.

Idea is to let scripts register a custom collection property, that the
asset view template can fill with the latest asset list contents and
pass that to the UI list.

Longer term I'd prefer if the UI code would support other containers,
and not rely so much on RNA and custom/ID properties. I have ideas and
plans for this, but meanwhile, this will do to remove the hacks.

Fix warning about possibly mixed C/C++ linkage of type

Would give a warning:
```
'ED_asset_library_reference_from_enum_value' has C-linkage specified, but
returns incomplete type 'struct AssetLibraryReference' which could be
incompatible with C [-Wreturn-type-c-linkage]
```

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

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).

Pose library: remove invalid flags

The wrong flags were used, and it works fine without flags as well.

No functional changes.

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

Store active asset library at workspace level

The Asset Browser still has its own active asset library. But for the UI
(e.g. the asset view UI template), there is one active asset library per
workspace now. This is needed because for technical reasons the property
has to be registered in C, ideally you could just register it as custom
property for any use-case and pass that to the asset view template.
Since this isn't possible, an active asset library per workspace seems
reasonable.

Merge remote-tracking branch 'origin/master' into asset-browser-poselib

Merge branch 'master' into ui-asset-view-template

Pose Library: get initial blend factor from RNA property

Pose Library: don't crash `POSELIB_OT_blend_pose` outside asset browser

Cleanup: update TODO

No functional changes.

Pose Library: blend quaternions properly, instead of LERPing them

This also removes the `bool flush_to_original` argument, as this flushing
is not required for the pose library (poses are always applied to the
original, and not to evaluated copies).

Cleanup: remove unnecessary `ATTR_FALLTHROUGH`

`ATTR_FALLTHROUGH` is only necessary when there is actually code inside
the falling-through `case`.

No functional changes.

Explicitly consider hidden bones as not selected