Search Issue Tracker
Fixed
Fixed in 6000.4.0b6, 6000.5.0a6
Votes
0
Found in
6000.4.0b6
6000.5.0a6
Issue ID
UUM-132372
Regression
No
[Windowing] Fix naming convention in Windowing API by using camelCase for public properties
Actual results:
Properties in Windowing.ResolutionChangedEventArgs and {}Windowing.{}{}PositionChangedEventArgs{} are using PascalCase.
They need to use camelCase, as pointed out here.
Expected results:
Properties in Windowing.ResolutionChangedEventArgs and {}Windowing.{}{}PositionChangedEventArgs{} are using camelCase.
.mem.xml and .api files are updated accordingly.
Reproducible with versions:
6000.4 and 6000.5
Notes:
This is only a property naming change in order to match the Unity public API guidelines.
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Fixed in 6000.4.0b6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.4.0b6