Blender Git Statistics -> Branches -> temp-depsgraph-layers

"Temp-depsgraph-layers" branch

Total commits : 12
Total committers : 2
First Commit : March 20, 2017
Latest Commit : March 30, 2017

Commits by Date

DateNumber of Commits
March 30, 20171
March 29, 20170
March 28, 20170
March 27, 20170
March 26, 20170
March 25, 20170
March 24, 20170
March 23, 20170
March 22, 20173
March 21, 20173
March 20, 20175


AuthorNumber of Commits
Dalai Felinto11
Sergey Sharybin1

Popular Files

FilenameTotal Edits

Latest commits Feed

March 30, 2017, 15:42 (GMT)
Merge remote-tracking branch 'origin/blender2.8' into temp-depsgraph-layers
March 22, 2017, 14:34 (GMT)
Layers Unittesting pep8: 2/2 (manual changes)
March 22, 2017, 14:31 (GMT)
Layers Unittesting pep8: 1/2 (mass changes)
March 22, 2017, 14:29 (GMT)
Merge remote-tracking branch 'origin/blender2.8' into temp-depsgraph-layers
March 21, 2017, 10:48 (GMT)
Fix crash when removing layer
March 21, 2017, 10:36 (GMT)
Make sure newly added objects follow layer collection evaluated flag
March 21, 2017, 09:51 (GMT)
Fix unittests

depsgraph need its own time to update before we can check results (or set selection)
March 20, 2017, 18:47 (GMT)
Layers: Remove old base visible / selected code
March 20, 2017, 18:44 (GMT)
Attempt to fix selection code (not working though)
March 20, 2017, 18:44 (GMT)
Adding missing DAG_relations_tag_update
March 20, 2017, 18:44 (GMT)
Blender 2.8: Initial hook of layer collections evaluation in DEG

This moves selectability/visibility flag flush from some hardcoded
places in the code to depsgraph. This way it is possible to simply
tag depsgraph to update those flags and rest it'll do on it's own.

Using depsgraph for such flush is an overkill: those flags are fully
static and can not be animated, so it doesn't really make sense to
hook only those to depsgraph.

However, in the future we will have overrides on collections, which
ideally would need to be animatable and drivable and easiest way
to support this is to do this on depsgraph level, so it ensures
proper order of evaluation for animation and drivers. And it seems
logical to do both overrides and flags flush from depsgraph from
this point of view.

This commit lacks two things:

1. Proper flag for DAG_id_tag_update(), so currently the only way
to inform depsgraph about nered to flush visiblity/selectability
flags is to tag scene ID for update. Flag of 0 will to the trick
for now.

2. Any operation which changes layer collections or render layers
need to tag relations to update. This is not done, so any change
to those will cause crash.
March 20, 2017, 18:44 (GMT)
Layers / Depsgraph: Unittesting for selection and visibility evaluation

MiikaHweb - Blender Git Statistics v1.06
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021