ATTN LOGOS: An annoyance when limiting search to a dynamic collection
This gets me every single time!
When I want to limit a search to a dynamic collection created on the fly (e.g., books by a certain author, or in the most recent case, books older than a certain date), I type in the rule for selecting those books and hit Enter.
But the search takes place only within one book, the first book in the TOP BOOKS section of the dropdown menu, which was highlighted by default, but which I was moving so fast as to not think about...yet again.
PLEASE, when what is typed into the Search box is obviously a collection rule, make the default selection be the NNNN books with {criterion} line. I would wager that 99.9% of the time that's what the user wants. Not some random first book in the list. Having to click to select the top line is an extra step. If someone really wants to search within only one book, they're going to need to be more careful about choosing the right one anyway. So for a quick search, where the user types the criterion and hits Enter, you really can probably assume the user wants to go with all books that match.
Comments
-
PLEASE, when what is typed into the Search box is obviously a collection rule, make the default selection be the NNNN books with {criterion} line. I would wager that 99.9% of the time that's what the user wants.
Well, 99.99% of the time!
Dave
===Windows 11 & Android 13
0 -
PLEASE, when what is typed into the Search box is obviously a collection rule, make the default selection be the NNNN books with {criterion} line.
+1 [Y] Please
Actually annoyance of a single selection default when NNNN results is in drop down => feels buggy to me.
Keep Smiling [:)]
0 -
This seems to have missed MJ's normal bump for attention because other people had already commented on it.
LOGOS, please fix this. The behavior is wrong IMO. I'm inclined to call it a BUG.
0 -
I agree with you Rosie
0 -
We do already have a case open for this issue. I've added a link to this thread in the case so that we can post an update in the event that this is fixed.
Andrew Batishko | Logos software developer
0 -
I'm glad to see this truly dumb behavior is on the list of things to fix.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
I'm glad to see this truly dumb behavior is on the list of things to fix.
Doesn't sound like there's any promise to fix it. Andrew said "in the event that this is fixed."
I think we need to pile onto a feedback suggestion. I've just created one.
VOTE HERE:
0 -
I voted.
0 -
Doesn't sound like there's any promise to fix it. Andrew said "in the event that this is fixed."
I make an effort to never promise fixes, with the exception of critical fixes that are currently in progress, or things that have already been fixed but not released. It's too difficult to predict the future and potentially leave people disappointed.
I struggle with finding the right way to state this that doesn't sound like I'm dismissing the problem and doesn't sound like I'm promising anything.
Andrew Batishko | Logos software developer
0 -
Doesn't sound like there's any promise to fix it. Andrew said "in the event that this is fixed."
I make an effort to never promise fixes, with the exception of critical fixes that are currently in progress, or things that have already been fixed but not released. It's too difficult to predict the future and potentially leave people disappointed.
I struggle with finding the right way to state this that doesn't sound like I'm dismissing the problem and doesn't sound like I'm promising anything.
I understand how any language can be interpreted differently by different folks. Thanks for giving us this insight on the words you do use.
0 -
Doesn't sound like there's any promise to fix it. Andrew said "in the event that this is fixed."
I make an effort to never promise fixes, with the exception of critical fixes that are currently in progress, or things that have already been fixed but not released. It's too difficult to predict the future and potentially leave people disappointed.
I struggle with finding the right way to state this that doesn't sound like I'm dismissing the problem and doesn't sound like I'm promising anything.
Thank you for your kind and careful explanation, Andrew. I didn't mean to sound irritated or impatient.
0 -
I didn't mean to sound irritated or impatient.
I definitely did not take it that way, and in fact, appreciated you setting up a feedback suggestion for people to vote on.
Andrew Batishko | Logos software developer
0 -
VOTE HERE:
Currently has 8 votes.
Keep Smiling [:)]
0
