Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b14
Issue ID
649533
Regression
No
The name of a new behaviour (if you searched by it) should be the same as your search value (if there are no matches)
(Inconsistency with "Add Component" feature behaviour)
1 Create new project
2 Create new Animator Controller
3 Create an empty animation state and select it
4 Click on "Add behaviour" button
Input "test" value into search field (you mustn't have such script in your project) and hit "Enter"
Expected result:
If search failed to find such behaviour it should suggest create a new one with THAT name as Add component feature does.
Actual result:
If search failed to find such behaviour it suggests to create a new one with EMPTY name
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Add comment