Blender Git Loki

Fix T68130: Over sensitive number button dragging

When continuous grab, cursor motion was mapped to the min/max.
This caused problems when int/float max values were used.

Now the range is clamped by a value derived from the click-step
so dragging numbers never increases it to an impractically large value.

Tasks: remove scheduler struct, there is only a global one now

Tasks: rewrite task scheduler and pools to use TBB

TODO: test performance
* Local queues in depsgraph
* Grain size in parallel range
* Iterators chunk size calc

Tasks: don't pass thread_id always, instead go through accessor

We should move away from using thread IDs and instead store any thread local
data in the TaskParallelTLS. Getting the thread ID will also be more expensive
with TBB and is not so well defined.

Task: remove local queue and scheduling mode optimizations

Hopefully no longer needed with TBB, but needs to be tested.

Tasks: use TBB for parallel range

Task: don't use suspended task pool for iterators

There is no apparent reason for this, and it has extra overhead.

Task: change func_finalize to func_reduce and func_free

In preparation of using TBB.

Tasks: split task.c into task_pool.cc and task_iterator.c

Tasks: move priority from task to task pool

Merge branch 'blender-v2.81-release'

make Float Range node work again

assert earlier when nodes were not inserted correctly

Fix errors in fix for T68018

GPencil: Add Vertex Color to N Panel

GPencil: Add a switch to Vertex Color panels

Merge branch 'functions' into functions-experimental-refactor

Merge branch 'master' into functions

UI: Rewrite stacked full-screen logic, fixing issues

To recreate the main issue:
* Set render and file browser to show in full-screen in the preferences
* Default scene, press F12 in 3D View
* Press Alt+S to save the image
* Escape the file browser
* Escape the image editor
The former 3D View would now show the image editor. This is a common
use-case that should work.

Full-screen code is a hassle to get to work as expected. There are
reports from 2.5, I did lots of work years ago to get these kind of
use-cases to work fine. But apparently I broke this one with a fix for
another common use-case in March (0a28bb14222c).
This now stores hints in the space, rather than the area, which should
make things much more controlable and hopefully help us fix issues like
this.
Here are a few references describing further common issues (all should
work fine now): 0a28bb14222c, e61588c5a544, T19296

Checked over this with Bastien, we agreed that at some point we should
do a big rewrite of all of this, for now this is acceptable.

GPencil: Replace default palette to Krita colors