Custom property in workspace "Layout" can not be added to driver #68319

New Issue

Realname · 2019-08-06T16:40:06+02:00

Realname commented

2019-08-06 16:40:06 +02:00

System Information
Operating system: Linux-4.10.0-28-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 17.0.7

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

When adding custom property in any workspace can't use it in any drivers. It works with object's custom property world's custom property, but not in workspaces.
I think it's a bug.

Thank's in advance.

workspace_custom_property_drivers.blend

**System Information** Operating system: Linux-4.10.0-28-generic-x86_64-with-debian-stretch-sid 64 Bits Graphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 17.0.7 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: (optional) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] When adding custom property in any workspace can't use it in any drivers. It works with object's custom property world's custom property, but not in workspaces. I think it's a bug. Thank's in advance. ![Screenshot from 2019-08-06 14-38-20.png](https://archive.blender.org/developer/F7651719/Screenshot_from_2019-08-06_14-38-20.png) ![Screenshot from 2019-08-06 14-38-40.png](https://archive.blender.org/developer/F7651721/Screenshot_from_2019-08-06_14-38-40.png) [workspace_custom_property_drivers.blend](https://archive.blender.org/developer/F7651723/workspace_custom_property_drivers.blend)

Realname commented

2019-08-06 16:40:06 +02:00

Added subscriber: @spacialy4

Germano Cavalcante commented

2019-12-24 12:39:02 +01:00

Added subscribers: @Sergey, @mano-wii

Germano Cavalcante commented

2019-12-24 12:39:03 +01:00

When opening the file, I came across an assert on this line , which is possibly related to the problem described.

>	blender.exe!DEG::DepsgraphNodeBuilder::build_id(ID * id) Line 465	C++

 	blender.exe!DEG::DepsgraphNodeBuilder::build_driver_variables(ID * id, FCurve * fcurve) Line 941	C++
 	blender.exe!DEG::DepsgraphNodeBuilder::build_driver(ID * id, FCurve * fcurve, int driver_index) Line 930	C++
 	blender.exe!DEG::DepsgraphNodeBuilder::build_animdata(ID * id) Line 871	C++
 	blender.exe!DEG::DepsgraphNodeBuilder::build_object(int base_index, Object * object, DEG::eDepsNode_LinkedState_Type linked_state, bool is_visible) Line 611	C++
 	blender.exe!DEG::DepsgraphNodeBuilder::build_view_layer(Scene * scene, ViewLayer * view_layer, DEG::eDepsNode_LinkedState_Type linked_state) Line 108	C++
 	blender.exe!DEG_graph_build_from_view_layer(Depsgraph * graph, Main * bmain, Scene * scene, ViewLayer * view_layer) Line 247	C++
 	blender.exe!DEG_graph_relations_update(Depsgraph * graph, Main * bmain, Scene * scene, ViewLayer * view_layer) Line 495	C++
 	blender.exe!wm_event_do_depsgraph(bContext * C, bool is_after_open_file) Line 367	C
 	blender.exe!wm_file_read_post(bContext * C, const bool is_startup_file, const bool is_factory_startup, const bool use_data, const bool use_userdef, const bool reset_app_template) Line 557	C
 	blender.exe!WM_file_read(bContext * C, const unsigned char * filepath, ReportList * reports) Line 675	C
 	blender.exe!wm_file_read_opwrap(bContext * C, const unsigned char * filepath, ReportList * reports, const bool autoexec_init) Line 2095	C
 	blender.exe!wm_open_mainfile__open(bContext * C, wmOperator * op) Line 2236	C
 	blender.exe!wm_open_mainfile_exec(bContext * C, wmOperator * op) Line 2273	C
 	blender.exe!wm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) Line 2461	C
 	blender.exe!wm_handler_fileselect_call(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, const wmEvent * event) Line 2560	C
 	blender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2956	C
 	blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3008	C
 	blender.exe!wm_event_do_handlers(bContext * C) Line 3387	C
 	blender.exe!WM_main(bContext * C) Line 420	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 520	C
 	[External Code]

@Sergey, your area?

When opening the file, I came across an assert on this [line ](https://developer.blender.org/diffusion/B/browse/master/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc$465), which is possibly related to the problem described. ``` > blender.exe!DEG::DepsgraphNodeBuilder::build_id(ID * id) Line 465 C++ blender.exe!DEG::DepsgraphNodeBuilder::build_driver_variables(ID * id, FCurve * fcurve) Line 941 C++ blender.exe!DEG::DepsgraphNodeBuilder::build_driver(ID * id, FCurve * fcurve, int driver_index) Line 930 C++ blender.exe!DEG::DepsgraphNodeBuilder::build_animdata(ID * id) Line 871 C++ blender.exe!DEG::DepsgraphNodeBuilder::build_object(int base_index, Object * object, DEG::eDepsNode_LinkedState_Type linked_state, bool is_visible) Line 611 C++ blender.exe!DEG::DepsgraphNodeBuilder::build_view_layer(Scene * scene, ViewLayer * view_layer, DEG::eDepsNode_LinkedState_Type linked_state) Line 108 C++ blender.exe!DEG_graph_build_from_view_layer(Depsgraph * graph, Main * bmain, Scene * scene, ViewLayer * view_layer) Line 247 C++ blender.exe!DEG_graph_relations_update(Depsgraph * graph, Main * bmain, Scene * scene, ViewLayer * view_layer) Line 495 C++ blender.exe!wm_event_do_depsgraph(bContext * C, bool is_after_open_file) Line 367 C blender.exe!wm_file_read_post(bContext * C, const bool is_startup_file, const bool is_factory_startup, const bool use_data, const bool use_userdef, const bool reset_app_template) Line 557 C blender.exe!WM_file_read(bContext * C, const unsigned char * filepath, ReportList * reports) Line 675 C blender.exe!wm_file_read_opwrap(bContext * C, const unsigned char * filepath, ReportList * reports, const bool autoexec_init) Line 2095 C blender.exe!wm_open_mainfile__open(bContext * C, wmOperator * op) Line 2236 C blender.exe!wm_open_mainfile_exec(bContext * C, wmOperator * op) Line 2273 C blender.exe!wm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) Line 2461 C blender.exe!wm_handler_fileselect_call(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, const wmEvent * event) Line 2560 C blender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2956 C blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3008 C blender.exe!wm_event_do_handlers(bContext * C) Line 3387 C blender.exe!WM_main(bContext * C) Line 420 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 520 C [External Code] ``` @Sergey, your area?

Germano Cavalcante commented

2019-12-24 12:46:44 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Sergey Sharybin commented

2019-12-24 14:41:37 +01:00

Added subscribers: @JulianEisel, @dfelinto

Sergey Sharybin commented

2019-12-24 14:41:37 +01:00

Workspace is an interface and it can not be used to drive anything in the scene. So this isn't a bug that driver doesn't work but rather expected behavior.

The issue, however, goes deeper than assert()in the code. Assert is easy to silence if needed, but it shouldn't be possible to select workspace as a source of driver.

What is unclear to me is what was motivation for making Workspace a reusable ID? It causes issues like this. Seems only forcing all sorts of workarounds in other areas. This is something for @JulianEisel or @dfelinto to look into.

P.S. Since the workspace is an ID I've tried to link it from one file to another and got the following error: Warning: Library file, loading empty scene.

Workspace is an interface and it can not be used to drive anything in the scene. So this isn't a bug that driver doesn't work but rather expected behavior. The issue, however, goes deeper than `assert()`in the code. Assert is easy to silence if needed, but it shouldn't be possible to select workspace as a source of driver. What is unclear to me is what was motivation for making Workspace a reusable ID? It causes issues like this. Seems only forcing all sorts of workarounds in other areas. This is something for @JulianEisel or @dfelinto to look into. P.S. Since the workspace is an ID I've tried to link it from one file to another and got the following error: `Warning: Library file, loading empty scene`.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Custom property in workspace "Layout" can not be added to driver #68319