Search Issue Tracker
Feature Request
Feature Request in 6000.5.X
Votes
0
Found in
2022.3.69f1
6000.0.66f1
6000.3.6f1
6000.4.0b6
6000.5.0a7
Issue ID
UUM-133711
Regression
Yes
No warning thrown when modifying array size while editing multiple objects
How to reproduce:
1. Open the attached "IN-132316_Repro" project
2. Open scene "Scenes/SampleScene"
3. In the Scene Hierarchy, select both Script A and Script B
4. In the Inspector, add or remove an element from the "Targeted Objects" array
Actual result: No warning is thrown and the array sizes of both objects are modified
Expected result: A warning is thrown informing the user that both objects will be modified
Reproducible with: 2022.1.0a4, 2022.3.71f1, 6000.0.66f2, 6000.3.6f1, 6000.4.0b6, 6000.5.0a7
Not reproducible with: 2021.3.58f1, 2022.1.0a2
Could not test with: 2022.1.0a3 (Can't open the project or create a new one. License errors are thrown.)
Reproducible on: MacOS 15.7.3 (User), Windows 11
Not reproducible on: No other environment tested
Notes:
- The warning is thrown correctly if trying to remove an object that is not the last one in the array
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
- "Custom Function" Node "Input" type changes do not immediately show mistmatch errors when set to an incompatible type in Shader Graph
- My Assets list is populated with Asset Packages when setting how many Packages to display before clicking the Load button
- Hub shows 6.0 as Latest LTS when opening a project after deleting its 6.3 Editor version
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
Resolution Note:
Thank you for sharing your feedback with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning.
More explanation on this: The pop-up originally showing the warning was here to warn about a bug previously happening where in a multi-selection, "untouched" array elements are getting overwritten on the other selected objects when the array is changed. This bug has been fixed and the associated warning removed.
From what we understand here, you would like a pop-up here for another behavior: Letting you know that array size on different object could be modified when adding/removing an item in the array. However, this is expected for multi-selection: Every changed performed to the multi-selection will propagate to the other elements. Having a warning about this when sizes are different could make sense indeed, but that a different feature than the one that was previously triggering the warning.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.
Resolution Note (6000.5.X):
Thank you for sharing your feedback with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning.
More explanation on this: The pop-up originally showing the warning was here to warn about a bug previously happening where in a multi-selection, "untouched" array elements are getting overwritten on the other selected objects when the array is changed. This bug has been fixed and the associated warning removed.
From what we understand here, you would like a pop-up here for another behavior: Letting you know that array size on different object could be modified when adding/removing an item in the array. However, this is expected for multi-selection: Every changed performed to the multi-selection will propagate to the other elements. Having a warning about this when sizes are different could make sense indeed, but that a different feature than the one that was previously triggering the warning.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.