Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.1
2020.2
2020.2.0a12
2021.1
Issue ID
1248669
Regression
No
[Quick Search] Error thrown on selecting Extension, Folder, File option under Excludes from "Search Index Manager" window
On selecting Extension, Folder, File option from the dropdown under "Excludes" cause the editor to throw below error:
"Drags can only be started from MouseDown or MouseDrag events
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)", refer attached video..
Steps to repro:
1. Create a new project
2. Window > Package Manager > Quick Search > Install (Preview.7 - 1.6.0)
3. Edit > Preferences > Quick Search
4. Asset indexing mode > Full Indexing > Create Index
5. Double click on the newly created index asset (this will open the Index Manager)
6. Search index Manger > Assets > Excludes
7. Change the option(Extention, Folder, File) from the dropdown
Actual Result:
"Drags can only be started from MouseDown or MouseDrag events" error is thrown on changing option from the dropdown under Excludes
Expected Result:
Excludes dropdown option is changed gracefully
Note: "Index Manager" feature is introduced in package version 1.6.0-preview.7
Occurring on:
2021.1.0a1, 2020.2.0a12, 2020.1.0b9 with package version 1.6.0 - preview.7
Environment:
Occurs only on Windows 10
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
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- ChangeSets are not detected when created via Editor Scripts
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
- BuildPipeline error is thrown when building Asset Bundles
- "IndexOutOfRangeException" errors appear when entering Play Mode if using "AsDeferredJobArray"
Resolution Note (fix version 2021.1):
Fixed Error thrown on selecting Extension, Folder, File option under Excludes from "Search Index Manager" window.
Details: EnumField and BasePopupField-derived controls would not react at the right moment to PointerDownEvents, letting other controls (including container-type controls like the ListView) to react prior to themselves, enabling Drag manipulations for instance, when they shouldn't.