Bible Search "while typing" not working.
I am using logos 4.2a beta 2.
The greatly appreciated Bible Search while typing function seems to be suspended in my program. I have it selected in the drop down, but it isn't working. While looking for "anxious," search while typing/ entire Bible/ ESV:
If I type "a" I get 9103 results in 6737 verses, when I get to "an" I get 1044 results in 991 verses. But when I get to "anx" I get zero, where it remains through each letter until I spell the entire word: anxious. Only then do I get 25 results in 23 verses.
What am I doing wrong?
Windows PC - Android Phone - Surface Pro 4
Comments
-
Michael March said:
What am I doing wrong?
Probably nothing, though I would expect to see results for 'anx', 'anxi'.
However, since you are running a beta version you would get a response from Logos if you reported this in the PC Beta forum!
Dave
===Windows 11 & Android 13
0 -
Michael March said:
What am I doing wrong?
This is exactly how speed search is supposed to work. When you type anxi, you're searching for the word anxi, not for words beginning with anxi - hence no results. 'a' and 'an' are obviously real words, hence results show at that stage.
Bible Speed search is of most value when you're entering multiple search terms.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Well I'll be jiggered. I was sure it used to race ahead with each letter typed before. As I know how to use wildcards, I can still get what I want but I thought it was different when it first came out a while back. It's always worked that way, huh?
Synapses ain't what they used to be...
As long as you're reading this, if you can tell me how to turn off my auto beta updates easily, go ahead. That'll save me having to continue trying to figure it out. Anyone who can't recall that simple a function isn't beta material.. [:S]
Windows PC - Android Phone - Surface Pro 4
0 -
Michael March said:
As long as you're reading this, if you can tell me how to turn off my auto beta updates easily, go ahead. That'll save me having to continue trying to figure it out. Anyone who can't recall that simple a function isn't beta material..
Use the command "Set Update Channel to Default" You will ride out the current beta cycle and then be returned to regular stable-user status. If you want the stable version now you will have to uninstall Logos 4, delete its files and completely reinstall it.
Prov. 15:23
0 -
Kevin Becker said:Michael March said:
As long as you're reading this, if you can tell me how to turn off my auto beta updates easily, go ahead. That'll save me having to continue trying to figure it out. Anyone who can't recall that simple a function isn't beta material..
Use the command "Set Update Channel to Default" You will ride out the current beta cycle and then be returned to regular stable-user status. If you want the stable version now you will have to uninstall Logos 4, delete its files and completely reinstall it.
Kevin, I don't think that will work. If one is on the beta channel and sets the update to default, one gets the default updates for the beta channel. At least that's how I understand how it works.
What you have to do is to revert to a stable release and then set the update to default.
But this is problematic once one has entered a beta path, since there are often resources and components that are loaded that will not work in the stable release. I don't know how to overcome this issue without an uninstall/reinstall (perhaps using one of the methods in the Wiki). BTW, I don't believe that setting the update channel to stable will work either. Doing that will not uninstall the beta components and reinstall the stable ones, as the update channel only looks for updates (not down-grades).
By far the simplest solution is to stay with the beta and ride it out until it gets to the gold release. If that release comes to the beta channel, then setting the channel to default will set it to the stable channel default. If that release doesn't come to the beta channel, then setting the channel to stable after the distribution of the gold release will do the same thing.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
No, Kevin is right. Setting the update channel to default now will mean you'll get all the beta updates for the current version (4.2a), but no more beta updates after that.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Richard DeRuiter said:
Kevin, I don't think that will work. If one is on the beta channel and sets the update to default, one gets the default updates for the beta channel. At least that's how I understand how it works.
Yes, it will.
The default channel for a Beta channel is Beta. BUT, when the Beta updates to a Release Candidate it will change its default update channel to the stable RSS. He used the command "Set Update Channel to Beta" which over-rides this default behavior. Setting the update channel to default now gives Michael the benefits of improving stability as the Beta matures. What setting the update to default will do is prevent him from getting RCs 2+ until the final version goes Gold, unless he manually downloads the installer.
Prov. 15:23
0 -
Kevin Becker said:Richard DeRuiter said:
Kevin, I don't think that will work. If one is on the beta channel and sets the update to default, one gets the default updates for the beta channel. At least that's how I understand how it works.
Yes, it will.
Oops, I misread your response. [sigh] I thought you told him that setting his channel to default would get him out of the current beta cycle and revert him to the stable channel.
Sorry for not paying closer attention.
Back to Bible study - where I hope I'm being much, much more careful!
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I started it, sorry! I remember when I set the update channel to beta, it was just a few weeks ago, and I did it because of something I think I read somewhere that said that 4.2 was a stable beta or some such designation which seemed reasonable to me at the time. Whatever it was I'm okay with it. Logos always seems to work fine for me, virtually every complaint I've had has been narrowed down to operator error[:P].
After reading these posts, it seems unclear what might happen to me if I try to get off this train, so I'll stick with it and try not to clog the forums with too many stupid questions.
In any case, thank you all so much for your tremendous support, I'm feelin' it.[Y]
Windows PC - Android Phone - Surface Pro 4
0 -
Michael March said:
After reading these posts, it seems unclear what might happen to me if I try to get off this train, so I'll stick with it and try not to clog the forums with too many stupid questions.
Sorry about the confusion! This update channel stuff has most people confused.
If you want to remain a beta tester do nothing. You will remain on the bleeding edge indefinitely.
If you want to leave the beta program use the command "Set update channel to default" and 4.2a will be the last betas you use. Even if you think you'll want to do more beta testing in the future, I still recommend using this command. You can always use the manual installer later if a future beta cycle has a toy you can't wait to play with.
Prov. 15:23
0
