Blender Git Loki

Cleanup: trailing newlines

Keymap: 2.7x macos-only additions

Keymap: add 2.7x keymap

This is the keymap from 929c78e33c06f55af4a3d98240959c4afcf9f39c
before the 2.8x keymap diverged from 2.7x.

All non-modal maps have been included.

Workbench: Use less GPU memory

When AA was enabled a new buffer was created. As the composite pass is
already done, we can reuse earlier buffers.

For the deferred rendering we reuse the color_buffer_tx and for the
forward rendering we reuse the transparect_accum_tx.

Workbench: Removed MaterialData UBO

Most of the times the materials differ due to the object_id. This was an
overhead and resulted in instabilities on Intel graphical cards. This
commit will revert the Material Data UBO and replace it with normal
uniform.

Merge branch 'master' into blender2.8

Cleanup: trailing newlines

Fix: Moving area edge could corrupt screen in very specific case

Caused by ca8f787349dcdf5. This issue is in master actually. Fixing it there
would cause conflicts so won't do that unless needed ;)

Steps to recreate were:
* Split properties editor into two (default startup.blend)
* Move both properties editors to the bottom, so only their headers are visible
* Move the upper edge of the upper properties editor up and down
Although it doesn't happen everytime, you may see the edge between the timeline
and the 3D view move, while the region drawing doesn't update.

What happened is area edge snapping allowed to snap the edge outside of window
bounds (we snap to a 4px grid by default), which screen_vertices_scale
interpreted as window scaling and thus run area size updates.

Merge branch 'master' into blender2.8

WM: Remove Screen Cast

This feature is better handled by specialized tools.

Change earlier fix to work with hiDPI

Referring to ca8f787349dcdf5. Thought in this case the simple `+ 1` would be
correct, but we need to make the same pixel adjustment as we do in other places.

Fix: Moving area edge could make areas overlap status-bar

Simply moving the properties editor of the default startup.blend all the way to
the bottom could trigger this. Calculating limits for area edge moving would use
screen bounds instead of entire window bounds (screen + global bars).

Added assert that should help debugging further issues like this.

Fix T55298: Failing assert when splitting areas vertically

There are more related glitches for which I have fixes. Will test them some more
and push in a followup commit.

UI: move UV selection options to left

This is consistent with the 3D view.

Fix: build error with msvc

introduced by rBd2757d149bf2d9ac604da6fb7f4742ee77e68d2d

Overlay: Make overlay engine rebder on top of paint modes.

This puts the wireframe on top of the weight in weight paint mode,
sculpt mode ...

Wireframe should be colored differently if the object is in paint mode
but it's not there yet.

Correct mistake checking version

Removed most calls to modifier_deformVerts_DM_deprecated()

None of those calls actually passed a DerivedMesh.

Alembic: speed up export of packed UV islands.

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

Make stdout unbuffered

Unbuffered stdout makes stdout and stderr better synchronised, and helps
when stepping through code in a debugger (prints are immediately
visible). We don't output much to stdout anyway, so this isn't likely to
cause any performance issues.