Right, it's not a bug. I realize now it is an unfortunate side effect of when Accordance implemented the quick entry feature. I knew this could not have always been the case. I have never paid attention to the Quick Entry popup, and have obviously trained my self to just ignore it altogether. I don't think I've ever used it in any meaningful way. But now that I'm paying attention to how it works, the current situation is unfortunate.
This is what I hear you saying:
"Now that we've implemented the Quick Entry box, you just need to…"
1. "…make the effort to followup your typing by hitting the escape key to remove a popup if you're ignoring it…", or
2. "…pay attention to the popup, decipher the list and mouseover to the item you want…"
"…in order to get the search to simply accept what you are actually typing as if it is the search you want."
That's not good.
It looks like the search entry box prioritizes a match under the "Verses" section, over an identical match in "Words", until it gets a complete exclusive match in the "Words" section. This makes sense to me.
However, it seems to me that making the search case-sensitive is the wrong approach, because it creates problems with book names that are also words in the text.
I can type "genesis" or "john" or "luke" or "romans" and hit return without engaging higher level thinking regarding the steps you're mentioning and get the book I want, but I can't do the same typing "song" or "job" or "psalm" or "proverb" or "mark" or "mat" or "revelation" etc.
If my window is set to search for verses, and I can't simply type "mat" or "song" and get the book I expect, then that's a design fail, and inconsistency in the work flow, where I think we can do better.
I think the benefits of having the Quick Entry box case sensitive are minuscule compared to the otherwise resulting confusing inconsistency on how to quickly lookup a book. How often are people searching for capitalized versions of common words and rely on the Quick Entry box's case-sensitive approach to speed along their process? Not near as often as users are typing "psalm" and expecting to be brought to the psalms, I would think. And remember, we're talking about when the search is set to find [Verses] even.
Another option to consider, which I would advocate for, would be prioritizing matches in the "Words" section of the Quick Entry box if [Words] is the current search mode.
Edited by Joe Weaks, 17 May 2016 - 01:51 PM.