Blender Git Loki

optimize adding multiple new values to multimap

only use new multimap implementation

fix issue with multiple links at same socket

better multimap implementation for a specific use case

missing from last commit

improved lookup or insert functions for map

Fix T59225 Screw modifier not displayed when using single vertex

Fix T66311: skin resize (ctrl+a) could crash

could happen when used on multiple objects with multi edit, and skin
modifier was not present on all participating objects

Reviewers: brecht

Maniphest Tasks: T66311

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

Merge remote-tracking branch 'origin/master' into soc-2019-fast-io

[Fast import/export] Fixed crash related to normal_iter and incorrect default aixs remapping behaviour

Fix T66165: RGB Curve node generates too bright color

The issue was that the end point would be extrapolated and it would lead to
very high values if the curve had a near inf slope. Now we use the actual end
point value and only extrapolate values that are outside of the start and
endpoint range.

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

Cleanup: rename variables for easier understanding

return index when value was inserted before

remove unnecessary template parameter

Cleanup debug print left in by mistake.

Thanks to @brecht for noticing it. :)

support storing multiple connected sockets per socket

add multiple new elements to multimap

Fix T66234: Issue on switching material mode between Object and Data

The root of the issue comes to the fact that part of dependency graph
is being removed, without doing any further remapping.
This was happening because only materials used by objects were pulled
in, so when material mode is changed some material became unused and
removed from the dependency graph and freed, causing object or its
data to point to a freed memory in its materials array.

Simplest and safest way to solve this is to pull materials referenced
by both object and object data. This causes somewhat higher memory
usage but keeps evaluated state of scene in an always consistent state,
without any need to tag/update object's data on material mode change.

Don't think it is a problem in practice.

Reviewers: brecht, fclem

Reviewed By: brecht, fclem

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

Fix T66353: VSE: Missing updates when moving strip with animation

iterate keys of multimap