Blender Git Commits

Cleanup: use shorter uchar, uint type names

Merge branch 'master' into soc-2016-pbvh-painting

added some previously missing tooltips

UI: Remove Palette Panel header

Merge branch 'blender2.8' into greasepencil-object

Code Cleanup: Replaced inlined layer-copying code with a call to the copy_ex() method

Fix: Make Single User wasn't supported for GP Objects

Fix: Doing a Scene "full-copy" wouldn't relink the gp_object

Fix: When transforming GP strokes in "Local" mode, the strokes would get obscured by
the transform constraint lines

Re-enable Amber asset engine.

Update Amber to take into account new View level.

Also get rid of hack mixing repo and asset uuid into same UUID, now we
do have a real repo UUID in API.

Everything seems to be be back on par with pre-View changes status.

Fix various mistakes and forgotten bits in previous 'Views' adding commit.

Core API code shall now be mostly functional again.

Fix: If the active object is not a GP object, starting to draw
with D-LMB would create a new GP object

This was behaviour was bad if you were trying to use GPencil for
anything other than 2D-3D art (e.g. for creating freehand input
for addons/Pose Sketching, annotating your work in EditMode, etc.)
as you could easily end up with all your annotations/sketches in heaps
of separate GP objects.

This commit improves the sitation slightly, by introducing an
"GPencil Object" property to Scene (similar to the existing "Active Camera"
and "Active Clip" settings).
* The idea is that the first GP object added to the scene as the "default
GPencil Object".
* Everytime you start sketching with GPencil AND the active object isn't
a GPencil Object, this "default GPencil Object" will become the active object,
and any strokes you draw will be added to this object (instead of a new
GP object being created)

TODO:
* Investigate if we can do this without losing whatever mode the user was
in previously. This new workflow makes GPencil a lot less useful for a
bunch of different annotation/addon workflows it could be used for in 2.7

Code Cleanup

Merge branch 'id_override_static' into asset-engine

Conflicts:
source/blender/makesdna/DNA_scene_types.h

Rename "Copy" color operator to "Rename"

Merge branch 'blender2.8' into greasepencil-object

Merge branch 'master' into id_override_static

Merge branch 'master' into soc-2017-normal-tools

Splash: Increase contrast of build info text

Now uses "Text Selected" theme color of "Menu Back" widget colors. Also
repositioned text slightly to have same margin on top and right (measured
by eye ;) ).
Tested with all bundled themes (contrib and no-contrib) and worked fine.

Considering that different splashes may need different colors for
overlaid text, using theme color may not be the best solution. I would
like to try how this works before adding an ugly way to force a certain
text color though.
Also tried different approaches, but this one I find the least ugly :S

As far as longer term plans go, we wanted to get a redesigned multi-page
splash screen anyway. At this point we can rethink how splash colors work
in general (i.e. auto-contrast, own splash theme colors, etc).