A) When emptying the search field, the results stick and don't reset.
For example, type something to get any (or no) results:
Then delete it (Backspace or Delete):
The results don't reset and the field's clearing cross on the right disappears. The only ways to get out of it is to manually close to the search results tab or to press Escape. It'd be nice if it were to reset by itself (like Everything and Windows Search).
B) I'd also very much appreciate it if the delay on the Search field could be removed or if there would be an option to do so, especially when using (Global) Everything search, to make it act similar to the Find/Filter field and to the Everything application. The current delay is the only reason why I still use Everything separately.
A) When you say "get out of it" do you mean go back to the previous folder? Clicking the Back button will do that.
B) Do you mean the delay after typing before the search begins? You can push Enter to trigger the search immediately without waiting. We could make the delay configurable, but I think you'd always want some delay there. Searching in Opus is never going to be as fast as directly inside Everything, there will always be some delay before results are returned, and so you need a delay before the search starts in order to have time to type your query.
A) Ah, then the Back button can be added to the Escape and Search tab closure options. Only it'd be nicer if it were to do so automatically when emptying the field (that the Search results tab closes or that it mirrors the folder one searched from). It saves some keystrokes or mouse movements.
Currently, there is a difference between an empty field not yet typed in, and one typed in (whether or not accidentally) and emptied out. Even though both look exactly the same, both when active (focused) and not.
B) If it would/could be as fast as Everything, I would prefer to have no delay there at all. That'd be a great option to have.
The way I use Everything the most is to search by media collections and adjacent media by filename. For example, I'd type 'IMG_0001', then Backspace the '(0)1' to see 'IMG_00(0)1-00(0)9' or replace such for more specific pieces of media. Or I use it to make truly any kind of search more specific in case there are many results. The instant result is key there, for I can type on right away (without having to wait or to press Enter each time in between).
Typing and moving on quickly is basically the overarching theme, as for both issues/suggestions.
It will never be as fast as Everything, because there is overhead involved in retrieving the search results. Data has to be copied from one process to another, and then the raw list of filenames has to be converted into the internal data structures Opus uses for its file lists.
Ah alright, understandable. Although, when I press Enter it gives the results pretty darn quick, so maybe even with the overhead it'd still be worth having it be without delay. But I guess I could only truly tell that in practice, for there being the slightest bit of time between typing the query and pressing Enter too of course, which might make it appear faster than actually the case.
@Jon Out of curiosity, as far as I gathered, you use IPC to communicate with ES right? I'd experimented with calling the DLL directly, which works pretty good by the way, but have zero experience as to if IPC is faster than calling some DLLs directly or not. Do you have any experience/insights on that, not just in ES context but also in general?
From my understanding the DLL is just a wrapper which handles the IPC communciation for you; at the end of the day the data still has to be copied from one process to another.
