Search Issue Tracker
Fixed
Fixed in 2023.2.X, 2023.2.0a21
Votes
0
Found in
2023.2.0a18
Issue ID
UUM-40107
Regression
No
Generated `UxmlObject` and `UxmlElements` are not being detected by TypeCache when they contain an attribute with default values
When an element contains an attribute that has default values in its constructor it will no longer appear in the UI Builder or be serializable from UXML.
The issue can be seen in the Editor log file where an error occurs in the source generator.
1) Add the following script to a project:
{code:java}
using UnityEngine.UIElements;
[System.AttributeUsage(System.AttributeTargets.All)]
public class DisplayNameAttribute : System.Attribute
{
public string Name { get; set; }
public string IconPath { get; set; }
public DisplayNameAttribute(string name, string iconPath = null)
{
Name = name;
IconPath = iconPath;
}
}
[UxmlElement]
public partial class MyElement : VisualElement
{
[UxmlAttribute, DisplayName("my name")]
public float myField;
}
{code}
2) Notice the element does not appear in the UI Builder Library. The Editor log file will contain an error message, however it wont be visible in the console.
3) Remove DisplayName from myField.
4) Element is now visible.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment