Search is now case sensitive by default?
I have noticed that since upgrading to 23.2.35 the inline search will no longer find any results with "abraham" for example, but will find "Abraham."
Can I change this in the settings? This was not the way search worked in the past, and it's not an improvement.
Comments
-
Can I change this in the settings?
Yes
Bible Search Match Case enabled results in Inline Search finding 0 (nothing):
Match Case disabled allows 249 results inline:
Screen shots in version 24.0 Release Candidate 1, which should update 23.2 next week.
Keep Smiling [:)]
0 -
...This was not the way search worked in the past, and it's not an improvement.
I agree that this is not a helpful default.
0 -
...This was not the way search worked in the past, and it's not an improvement.
I agree that this is not a helpful default.
I agree also. It caused me a bit of frustration when I was doing a bible search and "holy spirit" would not show up. It took me a while of searching to find out why. I don't know why the "either way" is not the default.
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
...This was not the way search worked in the past, and it's not an improvement.
I agree that this is not a helpful default.
I agree also. It caused me a bit of frustration when I was doing a bible search and "holy spirit" would not show up. It took me a while of searching to find out why. I don't know why the "either way" is not the default.
"Default" is meaningless as it is dependent on your previous setting in the Search tool (which may not be open). So, the Inline result may not match the setting in an open Search tab (confusing), and it has to toggled on/off to change the Inline result! Logos 9 Inline was still dependent on the previous setting in the Search tool, but it was less confusing to fix.
We need Faithlife to implement the the same settings for Inline search
Dave
===Windows 11 & Android 13
0 -
...This was not the way search worked in the past, and it's not an improvement.
I agree that this is not a helpful default.
I agree also. It caused me a bit of frustration when I was doing a bible search and "holy spirit" would not show up. It took me a while of searching to find out why. I don't know why the "either way" is not the default.
"Default" is meaningless as it is dependent on your previous setting in the Search tool (which may not be open). So, the Inline result may not match the setting in an open Search tab (confusing), and it has to toggled on/off to change the Inline result! Logos 9 Inline was still dependent on the previous setting in the Search tool, but it was less confusing to fix.
We need Faithlife to implement the the same settings for Inline search
Maybe a compromise? Say ... let user set the default....and then any change to that be temporary? As it is now... it seems that the only Default is the state of the last change.
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
Maybe a compromise? Say ... let user set the default....and then any change to that be temporary?
Well... No.This sort of thing has been discussed and users favored the Search tool opening to its previous settings, and that was implemented a couple of versions back. This applies even if you keep Search in your layout.
Dave
===Windows 11 & Android 13
0
