Blender Git Loki

Fix failing assert when reading workspace list from workspaces.blend

Merge branch 'master' into blender2.8

Depsgraph Cleanup, spelling

Depsgraph: Simplify logic around special case for node tree update

Depsgraph: Cleanup, extra whitespace

Depsgraph: Cleanup, use names for particle system tag flags

Depsgraph: Remove special exception logic from ID node tagging

This is something what we should be limiting as much as possible, it is
enough already to have special mapping cases in depsgreaph_depsgraph_tag.

math utils: Add utilities to scan bit and clear it

Math utils: Go away form naive code for highest_order_bit_uint

Math utils: Add bit scan operations

Math utils: Make it more clear what the functions are returning

Math utils: Cleanup, use _uint suffix for function which operates on uint

Possible solution for workspace mode

Basically implements the proposal made in [[https://developer.blender.org/T53389#474275|this comment]].
Important to note: This implementation keeps the mode stored in the object, the workspace takes care for setting it though.
Even if we decide to move the mode out of the object, most code here would still be valid. This is just a much more feasible approach that may suit our needs already.

The basic rule for setting the workspace mode is: The last active mode that is not object-mode (`OB_MODE_OBJECT`) becomes the workspace mode. Therefore the workspace mode must never be `OB_MODE_OBJECT`
By default new workspace use edit-mode as workspace mode.

Now, some parts of the design I'm not sure yet. Mainly:
* The implementation makes the workspace remember if the workspace mode or `OB_MODE_OBJECT` is active. Pressing TAB toggles between them. However the workspace doesn't try to keep the workspace mode active while only using `OB_MODE_OBJECT` as fall-back or when the user explicitly sets it. This differes from what I wrote in [[https://developer.blender.org/T53389#474275|mentioned comment]]. Maybe that's better maybe not.
* If the workspace mode isn't compatible with the currently active object, pressing TAB does nothing. In theory this may make sense, in practice it might be quite annoying though.

I'm not submitting that for code review really. Just for feedback on the general design approach and the discussion points mentioned above.

Subscribers: sergey, dfelinto

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

exposed meshisland constraints and modifier vertex groups to python

this was done to enable a new feature in the addon, the cluster editor.

refactored python object desctruction setup

no need to specify individual variables anymore - deletion now based on id

updated manta pp files

Fix missing refresh of editors when changing workspace view-layer

Needs to use new messaging system.

Depsgraph: Fix assignment to wrong flags

Tracking: Cleanup, fix typo in variable name

Fix merge errors

There was a problem with struct byte alignment.