Blender Git Loki

Fix for objects trailing in viewport when using BI in scene+Eevee in workspace

Thanks for Cl�ment Foucault for finding where to tackle.

Fixup for recent workspace changes: Python files

I wrongly changed some of these files via sed, and apparently overdid
it in some false positives.

Silence warning

Workspace: Call BKE_viewrender_free from the right place

We should call it when we free the workspace, not when removing it.
Patch by Julian Eisel.

Workspace: Move engines to workspace and Properties Editor cleanup

Engine is not stored in WorkSpaces. That defines the "context" engine, which
is used for the entire UI.

The engine used for the poll of nodes (add node menu, new nodes when "Use Nodes")
is obtained from context.

Introduce a ViewRender struct for viewport settings that are defined for
workspaces and scene. This struct will be populated with the hand-picked
settings that can be defined per workspace as per the 2.8 design.

* use_scene_settings
* properties editor: workshop + organize context path

Use Scene Settings
==================
For viewport drawing, Workspaces have an option to use the Scene render
settings (F12) instead of the viewport settings.

This way users can quickly preview the final render settings, engine and
View Layer. This will affect all the editors in that workspace, and it will be
clearly indicated in the top-bar.

Properties Editor: Add Workspace and organize context path
==========================================================

We now have the properties of:

Scene, Scene > Layer, Scene > World, Workspace

[Scene | Workspace] > Render Layer > Object
[Scene | Workspace] > Render Layer > Object > Data
(...)

Reviewers: Campbell Barton, Julian Eisel
Differential Revision: https://developer.blender.org/D2842

Fix compatibility flag for nodetree

NODE_NEWER_SHADING was introduced in e868b459bb8e however it should have been
added as a bitflag.

BKE_scene_uses_blender_eevee() was used in gpu_shader_output() as a workaround
for compatibility being poorly used.

Anyways this fixes this situation. This is necessary for an upcoming patch, even
though this is considered temporary - since the other NODE_*_SHADING values are
legacy from Blender Internal drawing.

Replace freeing checks with MEM_SAFE_FREE

Merge branch 'master' into blender2.8

WM: refactor gestures for use as tools

Border and circle select wait for input by default.
This commit uses bool properties on the operators instead of
magic number (called "gesture_mode").

Keymaps that define 'deselect' for border/circle select
begin immediately, exiting when on button release.

Fix T53054: Parentless bone + IK crashes

Cleanup: modal operator border callback names

Use same convention as all others.
Remove 'select' since these are used for zoom as well.

WM: store modal operator last-properties

Avoids modal operators needing to explicitly store them.

WM: Don't save mouse-paths to operator history

In preparation for modal operators storing their properties,
no need to keep mouse-paths around.

Also use generic function for lasso properties.

WM: remove hard-coded circle radius memory

Replace with operator type 'last_properties'.

Also use generic function for circle gesture properties.

Merge branch 'master' into blender2.8

Event System: Prevent mouse motion in click events

Don't convert mouse button events to click if they include dragging.
Double-click events already checked for this.

Cleanup: simplify lasso reallocation

Remove unneeded define, double allocations when increasing.

Cleanup: rename gesture mode to is_active

Wasn't obvious what this did at a glance.

Code cleanup: deduplicate primitive refit code.

Fix bad 'poll' prop callback API doc.

This was added to all prop types, when it is only available for Pointer ones.