Fix (studio-reported) issue in remapping code.
Not clearing runtime remapping data for the new ID as well as the old one can lead to false stale data there, wichi could e.g. make indirectly linked data be tagged as directly linked. This would generate an error report on file write when hapening on ShapeKey ID, since that type is not allowed to be directly linked.
This commit is contained in:
parent
a084839605
commit
74888cdbfd
|
@ -428,10 +428,13 @@ static void libblock_remap_data_update_tags(ID *old_id, ID *new_id, void *user_d
|
|||
}
|
||||
|
||||
static void libblock_remap_reset_remapping_status_callback(ID *old_id,
|
||||
ID *UNUSED(new_id),
|
||||
ID *new_id,
|
||||
void *UNUSED(user_data))
|
||||
{
|
||||
BKE_libblock_runtime_reset_remapping_status(old_id);
|
||||
if (new_id != NULL) {
|
||||
BKE_libblock_runtime_reset_remapping_status(new_id);
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
|
|
Loading…
Reference in New Issue