Inconsistency with users of object datablocks and silent deletion on Unlink #113547

New Issue

Simon Thommes · 2023-10-11T16:15:16+02:00

Simon Thommes commented

2023-10-11 16:15:16 +02:00

System Information
Operating system: Linux-6.5.6-gentoo-x86_64-AMD_Ryzen_9_5950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI
Graphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.113.01

Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-10 22:48, hash: 61dc86b0eb65
Worked: (newest version of Blender that worked as expected)

Short description of error

There is quite some inconsistency with how references and users of objects are considered when unlinking an object from the view layer. It doesn't seem clear from the user perspective when Blender will actually delete the object, when actually pressing Unlink and the behavior for collections is different in that it will just create a fake user when it is left without other users after unlinking.

I talked about this topic with @mont29 , who told me that this is a known issue which will need a lot of UI and design consideration before it can be changed. He told me to still make this report so we could keep track of the issue and not lose it out of sight. I'm not sure how this issue should be tagged though, as it's not strictly a bug report.

The most fatal issue with all of this is that the Unlink button for objects will actually not just unlink but delete the object entirely, when there is no real user left.

One solution to this particular issue that he proposed was to grey out the Unlink button whenever it would actually delete the object. Then the user would need to explicitly press the delete button instead, rather than Blender silently removing it.

**System Information** Operating system: Linux-6.5.6-gentoo-x86_64-AMD_Ryzen_9_5950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI Graphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.113.01 **Blender Version** Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-10 22:48, hash: `61dc86b0eb65` Worked: (newest version of Blender that worked as expected) **Short description of error** There is quite some inconsistency with how references and users of objects are considered when unlinking an object from the view layer. It doesn't seem clear from the user perspective when Blender will actually delete the object, when actually pressing `Unlink` and the behavior for collections is different in that it will just create a fake user when it is left without other users after unlinking. <video src="/attachments/4a9fe2c2-245d-4ec3-a195-f227799bc289" title="object_usage_inconsistency-2023-10-11_16.03.10.mp4" controls></video> I talked about this topic with @mont29 , who told me that this is a known issue which will need a lot of UI and design consideration before it can be changed. He told me to still make this report so we could keep track of the issue and not lose it out of sight. I'm not sure how this issue should be tagged though, as it's not strictly a bug report. The most fatal issue with all of this is that the `Unlink` button for objects will actually not just unlink but delete the object entirely, when there is no real user left. One solution to this particular issue that he proposed was to grey out the `Unlink` button whenever it would actually delete the object. Then the user would need to explicitly press the delete button instead, rather than Blender silently removing it.

object_usage_inconsistency-2023-10-11_16.03.10.mp4

9.5 MiB

Simon Thommes added the

labels 2023-10-11 16:15:17 +02:00

Richard Antalik commented

2023-10-11 22:45:26 +02:00