Why is NavigateFocusRing internal?

[ts_headfirst]

The NavigateFocusRing can be useful for overriding default navigation behaviour, but is is currently internal, why is that?

[ts_headfirst]

Hello, would any UI team member like to answer this simple question?

[NadaZilch]

I don’t know the context but this might help accessing internal UIToolkit members/classes without reflection:

How to check if a VisualElement is in world space or screen space?

You can use an AssemblyDefinitionReference to access internal members in UIElements. I actually use Assembly Definition References pretty often for cases like this. UIElements has quite a few internal members, and this lets you access them directly. This works because the UnityEngine.UIElements module (see AssemblyInfo.cs — UnityCsReference/Modules/UIElements/AssemblyInfo.cs at master · Unity-Technologies/UnityCsReference · GitHub) exposes its internals to UnityEngine.UI. [image]

[ts_headfirst]

Thanks for the suggestion, I had dismissed that idea since UI Toolkit is not itself a package.
But this actually works. Of course it would still be better if Unity would make these types public in the first place, but yeah…

Just to flesh out the exact requirements for this to work:

1. Create an AssemblyDefinitionReference
   

   

2. Create whatever files need internal references in the same folder or a subfolder, such that it is compiled as part of the UnityEngine.UI assembly.
   

   

You will of course then have to reference the UnityEngine.UI assembly, in all assemblies where you want access to your newly created type(s).