Official Quick Search Preview

The current behaviour is indexing on the first time,right? I think the current one is ok for me, it takes few minutes.
Is the new version indexing much more data and thus be slower?

 

Hi there,

I've noticed Quick Search doesn't seem to be working so well for me recently. I'm on 2.02 in Unity 2019.4. It just seems that I almost have to put in the exact item name and I have to do a lot of scrolling through to get to the file I'm trying to find. I thought it used to be a little looser?
Was there some way of marking files you search for often so they appear at the top of the list?

Thanks,
Pete

 

Thanks, maybe I'll try again adb v2 when I have some free time to see if things got better but it wasn't long ago I reverted to v1.

EDIT
It seem the issue is still there:
https://forum.unity.com/threads/assetdatabase-v2-refresh-significantly-slower-than-v1.802635/

 

The "ref:" search is not async right? I tried to run a search with that and it is blocking the UI since the search is quite slow(18 seconds).
The slowness is probably my fault, have several scripts where I simply used onValidate method to run some editor script without writing an editor interface, and I see that the search is firing the onValidate methods.
I need to clean these up, since these method slow down the build too.

 

Quick search has made Unity so much more usable! This is my second go-round with Unity, and I've always found the interface crude and unintuitive. Quick search really modernizes it. Thanks for your work on this!

 

On average a search however takes me 3 seconds on an intel 4770k and a crucial P1 ssd.
By the way, I found a bug.
When the editor lose focus, for example switching to another app, the search window disappear.

 

Hi @jonathans42!

I'm not sure if I'm using index files, how would I tell?
I tried cutting down the search items but assets covers so much stuff, not sure if it would be too much clutter but it might be nice to be able to prioritise say scenes and scripts over materials or something?

Oh also, when I choose the dockable window, it disappears if I select an item from the quicksearch. That doesn't sound right.

Thanks!

 

Hi, I am running 2019.4.1f1 and quick search 2.0.2 (and preview.3 - 2.1.0, haven't tested other versions) crashes the editor semi-randomly, though more often than not, when dropping an asset from the search window into the scene view, both when in a scene proper and when editing a prefab. I uploaded a bug report as well with the title "Dropping an asset from quick search to scene view crashes the editor". Don't know if you need any more information or if that's enough to at least take a look at!

 

Got a reply to my bug report as well, it has been fixed in 2020.2.0a18 as per https://issuetracker.unity3d.com/is...ing-the-window-from-which-the-drag-originated
It would be awesome if it was back ported, but good to know it already has been fixed.

Thanks!

 

Awesome, thanks for the help!

 

The only thing that I wish this tool would support...

 

Is there any API access to that?

Ie. could I write a thing that allowed me to right-click an asset, click an option, and get the result of searching for ref:asset as a list in my console?

 

Hey! Firstly, I've been really enjoying Quick Search, it's a massive workflow improvement, super handy!

Today I decided to create a custom Search Provider, and I must say the documentation isn't great. The example shown for registering a search provider appears to use the in-built provider for menu items, and it doesn't compile, because 1) it uses internal methods 2) the fetchItems lambda doesn't return anything. It's also only mentioned on a different page that you're meant to return null if not using the async method. Furthermore, to a new user, it's not very clear from this example if the missing method GetMenuInfo(itemNames, shortcuts) is responsible for anything important. As a new user, I would have really appreciated some standalone example code, that I could bring into my project, have it compile, and modify from there.


That aside, I've managed to get a provider working, but have hit a small issue. We're working on a card game, so I thought it'd be handy to have a way of quickly reviewing what a particular card does. This works, displaying the card's title, description and artwork as the Label / Description / Thumbnail.

Unfortunately, the search item's description GUI doesn't handle multi-line text nicely; it overlaps with other results (unless highlighted, which appears to draw over other results). I came across the "descriptionFormat" enum on SearchItem, and tried setting that to Ellipses, but that doesn't appear to do anything (at least in my case). You can see this below.

So my questions / comments are:

1. Is this a known issue, am I doing something wrong / is there something I can do about it?
   
   
2. Is there anything I can do about improving the search result order? Below, Strike is not the first result, when it preferably would be. I'm using very similar code to that shown on the documentation (SearchProvider.MatchSearchGroups), but have tried experimenting with the SearchItem score, with mixed results.
   
   
3. It would be fantastic if there was an additional "previewDescription" field/property, that defaulted to the normal description, that could be overriden to specify a different description for the full preview on the right hand side. If this were the case, I could display a short / trimmed description for each search result (and could do my own ellipsis trimming), and display a more detailed description on the right (for instance, you can see here, I'd also like to display the card Type and cost above the description (e.g. [Talent: 4-0]). I think this would be really useful even beyond my use case, as I can imagine several things I could search for where I'd want to display a more detailed description in the full preview.

And finally (sorry for the behemoth!), another thing that could improve a new user's experience, would be if we could get a base class SearchProvider that handled all the behaviour in the default way, and we just override whatever we need. Perhaps this exists and I didn't come across it, but if I could have inherited a provider that handles Asset / ScriptableObject queries in the default way (Enter/Click = Ping Object, Thumbnail = editor preview texture, Label = asset name etc), then I could have just overriden the label, thumbnail and description properties as needed (e.g. swap Thumbnail for a texture assigned to the ScriptableObject). Just a thought!

For reference, I'm on 2019.2 using QS 1.5.4. Thanks!

 

Great! I'll forward that to Open Project team as I think they are also unaware but plan to use ScriptableObjects a lot.

 

Can we somehow open default window with searched text in 3.0?

Doing for ex:

Code (CSharp):

1.  
2. var context = SearchService.CreateContext( SearchService.Providers, "a");
3. SearchService.ShowWindow( context );

Opens search with empty "searchText"

 

Would it be possible to add shortcut bindings to quick search so that I could navigate the results with Emacs-style

C-n

/

C-p

instead of the up and down arrows? It would make things so much faster. Thanks!

 

I will if I find some time. I've looked at source code and it seems like last saved value overwrites the one passed with SearchService.ShowWindow.

 

Kind of breaks after changing a scene:
1. Search for something that's used in different scene (with ref)
2. Open that Scene
3. Project provider doesn't work anymore

 

I mean by typing "ref:something" in search box

 

Certainly! I'm not actually sure how to do that, is there a standard link?

 

Jonathan helped me with my issues, here's what I've been trying to add to Unity


Code: https://gist.github.com/kamyker/9aea531fa3ee5083da869001df5a0ddf

 

Hey @jonathans42, I created a ticket as requested, here's a link to the issue in the tracker:

https://fogbugz.unity3d.com/default.asp?1284178_l79dsad94el07qfk

 

Thanks very much for all the info, sounds great

The TableView sounds very useful, but I doubt it'd work perfectly for me as whilst our cards are ScriptableObjects, very few of their SerializedProperties would be innately drawable (for instance, their description is just a localisation key, so unless I can supply a method / attribute that fetches the full string, it wouldn't display correctly).

Really my number 1 request would be to separate the description properties for entries vs their full preview on the right, as this would A) let me fix my issue with multiline text myself B) very straightforward / I can fetch whatever strings I want C) offers a lot of flexibility without the potentially overwhelming amount of information that might be displayed in a TableView.

 

I also have the same criticism as Tweedie regarding the API, it takes a LOT of work just to display some assets into a custom search provider. The issue is that the existing search provider are providing information that is too granular, since most people who will use this API will be more interested in supplying higher-level information like whole assets.

Great idea with the TableView, QuickSearch is rapidly evolving into something more. If the table view with columns is able to work with arbitrary components and scene objects, it wouldn't take much more for Quick Search to also act as a generic 'database' tool for querying and browsing frequently needed information. Used in conjunction with lights in the scene, light probes, etc. artists would be elated.

Aside from this, is it currently possible to access saved searchs in the input box as if they were search tokens? E.g. in our issue tracker, I can create a saved search named 'foo' with some query, and then use `#{foo}` as a placeholder for that query, then I can continue with more criteria or text. Currently I have to select the saved search manually to use it which greatly limits its usefulness.

 

Does

ref:

work with other filters? I tried looking for the references of a file and tried to use

t:prefab

alongside in order to only look for the prefabs in dependencies, but it gave no results. Same with Labels. Using just

ref:

works fine.

 

When using the search I was thinking about a way to save a selection in the search results to a new saved search.
How about if we could just select the items and drag them to the saved search panel on the left side?

 

Hi,

I am totally fresh in Unity and when I want to add this addon to Unity in HDRP fresh project i have such information:



What kind of error I am looking at

 

It seems that "file extension" searches do not return assets right now.

Could you add that?


(t:scene Thumbnails works but is much slower to type; also does Thumbnails t:scene)

Essentially I think adding a "." at the end of anything should not return folders anymore; adding more than a ".", say ".u" should only return files with that extension.

 

Is there any way to set the location of the quick search window? I love the drag and drop feature, but right now the window completely covers the scene view.. which is where I want drag the object. (In this case, onto a table in the scene).

Alternatively, when dragging / dropping, the quick search window could be faded / hidden.