Search Issue Tracker
Fixed in 2019.3
Fixed in 2019.1, 2019.2
Votes
1
Found in
2018.3.0a7
2018.3.11f1
Issue ID
1141886
Regression
Yes
[UI Elements] Play mode Color tint is not removed when Play mode cannot be entered due to compiler errors
To reproduce:
1. Open any project
2. Change editor's Play mode tint color to something clearly visible (File > Preferences > Colors > Playmode tint)
3. Create a script with compiler errors
4. Enter Play mode
Expected: tint is removed after unsuccessful attempt to enter Play Mode
Actual: tint remains applied to GUI objects (it seems to only affect editor window with UI Elements content, i.e. settings window)
Reproduced in: 2018.3.0a7, 2018.3.12f1, 2019.1.0b10, 2019.2.0a10
Not reproduced in: 2017.4.25f1, 2018.3.0a6
Note: since 2019.2.0a9, the tint is removed from main toolbar, but is still applied everywhere else
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
- Results of Texture ScaleMode is not intuitive when parent has a width or height set to pixel value and the other is set to auto
- Crash regression on ComputeShader inspector "Compile and show code" button
- Silent Crash on Windows when opening a project created in Ubuntu
- Profiler mouse and keyboard navigation is inconsistent and skips entries when analyzing Instantiate calls from a unit test
- Unmaximizing Editor Window results in a new window being created and deleted
APSchmidt
Apr 04, 2019 16:37
Nasty little bug; makes everything awfully confusing.
When I noticed it first, I thought that the editor was in Play mode and I couldn't understand why clicking on the play icon didn't make the editor get out of Play mode...