Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0b9
Issue ID
967937
Regression
No
Operators == and != are not implemented for Color32
Steps to reproduce:
1. Create a new Project
2. Create a script with 2 Color32 variables
3. Try to compare them with == or != operators
Expected result: colors are compared
Actual result: operators are missing errror
Reproduced on 2017.1.2p3, 2017.2.0p1, 2017.3.0b9, 2018.1.0a3
Notes:
- Color class can use the operators and be compared with Color32
- Color class comparison with == or != or isEqual is slow compared to checking r,g,b and sperately. The attached project demonstrates this discrepancy
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Replaced by task on scripting backlog