Search Issue Tracker
Fixed
Fixed in 6000.3.11f1, 6000.4.1f1, 6000.5.0a9, 6000.6.0a1
Votes
0
Found in
6000.3.0f1
6000.4.0a5
6000.5.0a2
6000.6.0a1
Issue ID
UUM-128715
Regression
No
Certain Painter2D properties are missing the get accessors
How to reproduce:
- Create and open a new project
- Import the “Test.cs“ script
- Observe the Console
Actual result: 4 errors for the “painter.fillGradient“, “painter.dashPattern“, “painter.fillTexture“, and “painter.strokeFillGradient“ properties are thrown
Expected result: No errors are thrown
Reproducible in: 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Could not test in: 6000.0.63f1, 6000.2.14f1 (The four properties have not been introduced yet)
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Note: All errors read: “The property or indexer ‘[property]’ cannot be used in this context because it lacks the get accessor“
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1