Blender Git Commit Log

Barebones for managing session changes

Adds initial OpenXR event querying so that session state change events
can be handled. Doesn't do any handling yet.

better explanation for lazy-init macros

Merge branch 'master' into cycles_improved_equiangular_sampling

Merge branch 'master' into feature_overrides

remove unused include

GPencil: Create new set of brushes for Win32 damaged files when use primitives

Some old Win32 files could have the brushes damaged and this produces a segment fault. Now, if the brush is damaged, a new set of brushes is created.

Related to T61413

simplify naming for lazy init macros

lazy init: thread safe registration and utility to list all

Outliner: Finish walk select

Adds walk in and out for walk select (left and right arrows)
If an element is closed, walk in will open the element. If
the element is open, left will close it. Otherwise left moves the
active element to the parent.

Merge branch 'master' into soc-2019-outliner

GPencil: Backbone Stretcher modifier

Merge remote-tracking branch 'origin/master' into soc-2019-npr

Revert changes from 'make format' on files unrelated to branch

Fix another build error

Reversed order of sampled X and Y to match default profiles

Enable graphics extensions if available

Check if available extensions includes the GL one, or the DirectX one on
Windows. Enable them if available.

Fix T65502: Crash when moving Collection into disabled Collection

Fix branch build error on windows.n Increase max bmesh operator slots

Outliner: Fix drawing of collection with disabled parent

If the layer collection had a parent that was disabled we wouldn't draw
it altogether.

Note: In this case I'm moving any enabled collection with a disabled
parent up in the hierarchy.

All in all I'm happy with this but I would like us to tackle the 1-20
shortcut, Ctrl+H menu and Collections viewport panel to do something
similar.

GTests: BLI_task: Add basic tests for BLI_task_parallel_listbase(), and some performances benchmarks.

Nothing special to mention about regression test itself, it basically
mimics the one for `BLI_task_parallel_mempool()`...

Basic performances benchmarks do not tell us much, besides the fact that
for very light processing of listbase, even with 100k items,
single-thread remains an order of magnitude faster than threaded code.
Synchronization is just way too expensive in that case with current
code. This should be partially solvable with much bigger (and
configurable) chunk sizes though (current ones are just ridiculous
for such cases ;) )...