Search Issue Tracker
Fixed
Votes
1
Found in
5.3.5f1
Issue ID
799597
Regression
No
FindScriptByClassName Does Not Account for Namespace-Qualified className
Icons for Scriptable Objects with namespace are displayed incorrectly (default asset icon).
To reproduce:
1) Open the attached project.
2) Go to the Assets folder.
- In the Editor folder there are 2 scripts 'SampleScriptableObject1' which uses a namespace and 'SampleScriptableUnity2' which does not. There are also 2 scriptable objects 'New Sample Scriptable Object 1' and 'New Sample Scriptable Object 2' derived from the scripts.
- The icon of 'New Sample Scriptable Object 2' is shown as the default Unity asset icon, even though the script associated with it has a green icon. The scriptable object derived from the script which doesn't use the namespace is displaying as expected.
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Prodigga
Jun 06, 2017 02:02
Nevermind - just something funky happened, had to reimport the assets with the icons to make it appear after I changed the scripts namespace.
Prodigga
Jun 06, 2017 02:02
Nevermind - just something funky happened, had to reimport the assets with the icons to make it appear after I changed the scripts namespace.
Prodigga
Jun 06, 2017 01:52
Still an issue in 2017.1 guys