Depsgraph: Remove unneeded `RNA_path_resolve`
Found during research of {T77124}. In `build_driver_data` an identical RNA_path is resolved twice. In stead of resolving it twice this patch will construct the `property_exit_key` based on the resolution of `property_entry_key`. This change isn't noticeable for users. Just a cleanup as it isn't needed to do the same logic twice. Reviewed By: Sergey Sharybin Differential Revision: https://developer.blender.org/D7872
This commit is contained in:
parent
752139556f
commit
0749cff957
|
@ -1 +1 @@
|
|||
Subproject commit 5d33d1a1c2531e64bda78d46b517571f2b1e98e7
|
||||
Subproject commit 36cc6368b7abee3bc1a47759107797117eb7d539
|
|
@ -1500,7 +1500,10 @@ void DepsgraphRelationBuilder::build_driver_data(ID *id, FCurve *fcu)
|
|||
}
|
||||
}
|
||||
if (property_entry_key.prop != nullptr && RNA_property_is_idprop(property_entry_key.prop)) {
|
||||
RNAPathKey property_exit_key(id, rna_path, RNAPointerSource::EXIT);
|
||||
RNAPathKey property_exit_key(property_entry_key.id,
|
||||
property_entry_key.ptr,
|
||||
property_entry_key.prop,
|
||||
RNAPointerSource::EXIT);
|
||||
OperationKey parameters_key(id, NodeType::PARAMETERS, OperationCode::PARAMETERS_EVAL);
|
||||
add_relation(property_exit_key, parameters_key, "Driven Property -> Properties");
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue