With some characters, "find-as-your-type" in find mode gives me an error (highlights the bar in red) as if there were no match even though there actually was. I can't figure out the logic behind it.
But isn't that weird?
For the first character, except when it matches the first character of a file/folder, it is considered as not conclusive (it is highlighted, but the file/folder does not get selected). As soon as you type a second character, it is considered ok.
1 Like
(Edit: Duplicated what PassThePeas said a bit, as I was typing in parallel.)
Preferences / Filtering and Sorting / Find-As-You-Type / Find Mode: Search anywhere in the filename only affects what happens when you type more than one character.
With that turned on:
-
If you type a single letter, it will only jump to files that start with that letter. If no file starts with the letter, it won't match anything and turns red to indicate that.
-
If you type more than one character, it will match names that have those characters anywhere in their names.
For completeness, if it's off:
- Whatever you type will only match filenames that start with the same character(s).
The logic is that a single letter will typically appear in a lot of files, and if you're only typing one letter you probably want the more standard (e.g. in File Explorer and early Opus versions) behavior of jumping to that letter in the list, or (if you did want to search anywhere in the names) you'd be better served by using the filter bar to show just the files with that letter in order to select one.
(Highlighting is controlled via an independent option. So you can always highlight matches elsewhere in the name even if you only want to jump to files that start with what you typed.)
1 Like
Thanks guys
Explained like that, it makes sense
However, a condition that could be improved is the option "Indicate matches in scrollbar" that only works if you have a vertical scrollbar because if you use the horizontal one (List view) the bar is hidden by the FAYT bar