Say I have twenty projects open, some small, some quite large. With one of the small projects selected, I open the Go to File dialog. The "Prefer Current Project" checkbox is checked. I type the name of a file which is in fact in this (small) project. A couple of minutes and 2% of my battery power later, "Searching..." is replaced by that one search hit. Evidently all of the open projects were searched, and then the result was displayed.
So what was the point of checking "Prefer Current Project"? What I expected was for the current project to be searched, the expected hit to be displayed in a second or two, and "Searching for more..." to be displayed in case I really was looking for a file with a similar name in another project and was willing to wait for it.
Awkward workaround is not to use GtF at all, but select the project node, Ctrl-F, and put the filename into the second search field.
I think, it is the same issue as for "Go to Type" described in the Bug 121389.
Seems we need use "Scope" options in all dialogs providing search and navigation to get additional info from a user about expected search results.
Knowledge about a desired scope of searching will let us optimize these processes of searching.
Unfortunately, resolving of this issue should be readdressed to the next release.
Obsolete target milestone. Changed from 7.0 to TBD
Fixed as explained, when files from index are known they are displayed.
The file list is then updated by files found by file system crawling.