pango wrote: ↑Sun Jul 14, 2019 11:51 am
Yes, results are by order of decreasing relevance first, then alphabetic order second. So I don't think returning slightly too many results is an issue.
I don't know how to explain this any better, so I'll try again. Every "Blessed" entry on this list is needless. There is no chance that I meant to type Blessed instead of Bleed. It's not a match, it doesn't contain the string I typed. That it contains the letters I typed is meaningless when exact matches for bleed were found. They then show up before
Bleeding Redeemer, which makes Bleeding Redeemer something you have to scroll past them to see.
There's some kind of far-reaching suggestion code going on here that only works well on long strings, and interferes hardcore on short ones. If I type in "Hearmsly Manor" it offers me "Hearthsly Manor". Ok, neat. But if I type in just "Hea", "Hearthsly Manor" doesn't even show up. If I type in "Heart", the very first result is "The Tombs of Hearthston" followed by a bunch of towns that actually start with "Heart".
I don't really understand your explanation of what gets priority in the list. It should be as simple as
-show things that start with typed string first.
-then show things that merely contain the string.
-alphabetize both groups and display the list.
Also, for what reason can't the results show up in real time as you're typing, so you don't have to commit to typing too little or too much? Unless the searching is intensive, I don't see why committing to a string before seeing results is necessary. You could just do something like this: