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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fixed in 6000.4.0b6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.4.0b6