Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0b7
Issue ID
916832
Regression
No
Multi - editing a property changes it only for one object if objects have custom inspector with CanEditMultipleObjects attribute
To reproduce:
1. Open the project, attached by tester (multipleObjectsEdit.zip)
2. Open "test" scene
3. Select a, b and c game objects in the Hierarchy
4. In the Inspector, change 'Test field' value
5. Select each of those game objects individually
6. Observe the 'Test field' value
Expected: multiediting a value changes it for all components on selected game objects
Actual: value is changed in only one game object's component instead all selected when using custom inspector with CanEditMultipleObjects attribute
Reproduced in 5.5.3p2, 5.6.1p2, 2017.1.0b7, 2017.1.0b8, 2017.2.0a1
By design: In order to write inspectors supporting multi selection, one needs to go through SerializedObject/SerializedProperty.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment