Search Issue Tracker
By Design
Votes
0
Found in
2022.3.55f1
6000.0.32f1
6000.1.0b1
Issue ID
UUM-91902
Regression
No
The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
Steps to reproduce:
- Download 6000.1.0b1 build
- Create a 2D project
- Select a "Main Camera" object in the "Hierarchy" window
- Go to the "Inspector" window
- Click the"Add Component" button
- From the "2D Animation" select, for example, the "Sprite Library" component
- Click the kebab menu and observe that "Paste Component as New" is disabled
- Select "Copy Component"
- Click the same kebab menu and observe that "Paste Component as New" becomes enabled
- Click it.
- Observe the result in the "Console" view
Actual results: The console displays an error "Can't add 'SpriteLibrary' to Main Camera because a 'SpriteLibrary' is already added to the game object!". Attachments are added below.
Expected results:
- Option "Paste Component as New" should stay disabled in the same game object/component. It is not good that we allow to do an action but as a result, we present an error.
- Option "Paste Component as New" should become enabled for another object/component.
Note: Seems the "Tilemap" component with the mentioned functions works differently as I described in the "expected Result" section.
Reproducible with versions: 6000.1.0b1, 6000.0.32f1, 2022.3.55f1.
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): Apple M1 Max
Comments (1)
-
lacreshanelson4
Jan 04, 2025 15:30
Fake
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
This is behaviour as designed. If we disable the menu item instead, the user wouldn't know why the action can't be performed.
The error is intended so the information is available to the user.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.