Search Issue Tracker
Won't Fix
Votes
9
Found in
2021.3.10f1
2022.2.0b8
2023.1.0a11
2023.2.0a1
Issue ID
UUM-15645
Regression
Yes
Array values aren't changed when altering them in a custom EditorWindow
How to reproduce:
1. Open the user’s attached “BB_ReportBugProject” project
2. Open the “Window → Configuration” window from the menu
3. Change any array value
Expected result: The array value is changed successfully
Actual result: The array value isn’t changed
Reproducible with: 2020.2.0a13, 2020.2.6f1, 2021.1.0a1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Not reproducible with: 2020.2.0a12, 2020.2.7f1, 2020.3.40f1
Reproduced on: macOS 12.5 (Intel), Windows 10
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
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
Resolution Note:
The fix would require making lengthy and risky changes to ReorderableList control. In order to avoid that we've converted users' editor window to UI Toolkit and verified the issue does not reproduce both in the newest Unity versions and 2020.3 LTS with the reworked window.
If experiencing the same issue, we recommend users consider converting their problematic IMGUI windows to UIToolkit.