Blender Git Loki

Merge branch 'undo-experiments' into undo-experiments-swap-reread-datablocks

Conflicts:
source/blender/blenloader/intern/readfile.c

undoexp: cleanup/simplify handling of WM/SCR/WS IDs.

Re-read from memfile WindowManagers, Screens and WorkSpaces
are never actually used in undo situation. This allows us to simply
early abort on those ID types, even if we do not find them in current
(old) bmain for some reason.

Merge branch 'greasepencil-object' into greasepencil-refactor

Merge branch 'master' into greasepencil-object

Merge branch 'undo-experiments' into undo-experiments-swap-reread-datablocks

undoexp: style cleanup.

Merge branch 'master' into new-object-types

Overlay: Move Alt+B clipping bounds display from workbench to overlay

GPencil: Use stack order for build modifiers

With the new evaluation, is possible to evaluate the modifiers in stack order.

This fix T66744

GPencil: Basic parenting working

Still looks one frame late.

GPencil: Include original reference to layer in runtime data

GPencil: Move parent matrix function to BKE module

Also, the function has been renamed to use a better naming.

undoexp: initial implementation of ID swapping.

Goal is to reuse same address also for changed IDs during an undo step.
This will allow for a given ID to almost always keep its same address
along a whole editing session, reducing a lot useless updates required
by current memfile undo.

Note that this commit has a lot of things to be investigated & fixed
still, at the very least:
* Refcounting is not really taken care of yet. This is fine for now
since we remap everything still, but at some point plan is to not remap
(liblink) reused unchanged IDs at all...
* We keep the double libmap for now, getting rid of it requires further
investigations (especially in some corner cases).
* 'UI' IDs (WM, screen and WS) are likely troublemakers given their
current weird specific handling. This might actually be seriously
simplified with this new approach?
* Since even changed IDs keep the same address, we are going to have to
improve a lot the `id->recalc` handling - unless we accept a
brute-force complete depsgraph update of the changed IDs.

Last point is especially interesting, as with current code, updates do
happen as expected most of the time (proper updates are missing
sometimes). This means that even undo moving of a very highly
modifier-subdivided object can be done "instantaneously" as that object
updates does not requires a geometry update.

Handling it properly will likely require to store the 'future' update
flag (as we do currently with the future unchanged status). Not sure
we'll catch all cases though, if that goes too far we may just force
full update as a first step. :/

undoexp: BKE_id_swap: add 'full' swapping.

Add a new func to do a full swapping of two ID data, including all of
the ID strcut content itself.

Also make both idswap functions resilient to a NULL given bmain pointer
(they simply do not do internal remapping of pointers to itself then).

Merge branch 'master' into newboolean

Merge branch 'master' into undo-experiments

Fix render settings not showing up for workbench engine

Merge branch 'undo-experiments' into undo-experiments-swap-reread-datablocks

Merge branch 'master' into undo-experiments

Merge branch 'greasepencil-object' into greasepencil-refactor