Blender Git Loki

GPencil: Replace Enable Fading with Enable Fade

Also changed property name

GPencil: Change default name of Vertex Color modifier

GPencil: Enable modifiers visible in Edit mode by default

Merge branch 'master' into new-object-types

GPencil: Replace Vertex Color ON/OFF by Enum

The old switch looked that disable the colors instead to change of mode.

Fix a few places that missed the new build option

GPencil: UI - Replace Duplications with Duplicates

Objects: add WITH_NEW_OBJECT_TYPES build options

Hair and pointcloud objects are now hidden from the UI and API by default.

GPencil: UI - Replace Add GP modifier eith Add modifier

GPencil: Fix crash when rendering in new window

This was caused by an incorrect context switch.

Merge branch 'master' into new-object-types

GPencil: UI - Remove Vertex Color text from popover

GPencil: UI - Smooth modifier replace Step with Repeat

GPencil: UI - Replace Object by Mirror Object

GPencil: Fix typo error

GPencil: Cleanup more loops with FOREACH macro

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

Merge branch 'id-ensure-unique-memory-address' into undo-experiments

Ensure IDs get unique memory addresses withing q given editing session.

Disclaimer: this should be considered as an engeneering, explanatory patch.

Rational: for undo work, we are now manipulating IDs from potentially many different 'memory realms' (in contrast to current undo system, where, since we always reallocate the whole main database at each undo step, we only ever have to deal with two, the old one from the memfile, and the new one from re-read data from that memfile).

So far, new undo system has used ID names-based search to remap old to new pointers, but this is slower, less safe, and forces us to do full undo barrier e.g. when renaming an ID.

Idea of this patch is instead to ensure that within a given editing session, we never ever allocate a data-block at the same address twice. That way, we can consider ID pointers as valid UIDs withing that scope, and use their values to handle remapping in udo steps even in case an ID has had several memory addresses in the history of the editing session.

This patches does two things:
# Add a way to ensure a newly allocated ID gets a memory address never used before for any ID.
# Store the history of all memory addresses ever used by a given ID.

Note that point 1 above is currently using a fairly simple and naive solution, but also quiet innefficient (just allocating again and again until we get a 'free' address), we can imagine a much more efficient solution if we go deeper in MEM_ allocator system itself. Not sure if it is worth it though, as with new undo system actual re-allocation of a same ID at a different address should be fairly rare (i.e. history of used/forbidden addresses should remain quiet short).

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

Merge branch 'master' into id-ensure-unique-memory-address