Searching using a wildcard character in a Bible tab
Comments
-
It works in Inline search if you're NOT using the new resource toolbar, yet another thing that appears to have been broken in the new inline search. I left the beta channel. The old toolbar works so much better for me that I'm considering canceling the subscription if this isn't changed.0
-
Jonathan Huber said:
It works in Inline search if you're NOT using the new resource toolbar, yet another thing that appears to have been broken in the new inline search. I left the beta channel. The old toolbar works so much better for me that I'm considering canceling the subscription if this isn't changed.
Yeah, I'm not a fan either. How do you get out of the beta channel?
0 -
Mark Allison said:
However, I can't figure out how to do the same thing when it's a Greek or Hebrew Bible. Am I missing something, or is it simply not possible?
I'm unable to recreate the problem you are reporting. Can you state which Bible you are search and what you are using for your search string?
Also can you try the search you are attempting in the full Search panel (with a Bible or Books search of that specific Bible) to see if it works there?Andrew Batishko | Logos software developer
0 -
Mark Allison said:
How do you get out of the beta channel?
There are instructions in the pinned post in the Beta forum: https://community.logos.com/forums/t/223736.aspx
Andrew Batishko | Logos software developer
0 -
Mark Allison said:
How do you get out of the beta channel?
run Set Update Channel to Default in the command box
0 -
Andrew Batishko said:
Also can you try the search you are attempting in the full Search panel
It works in the full search panel. I think the issue was (as Jonathan pointed out) that I'm on the beta channel and it's a bug in the beta. As you can see, there's not even a way to change keyboards in the beta.
0 -
Andrew Batishko said:Mark Allison said:
How do you get out of the beta channel?
There are instructions in the pinned post in the Beta forum: https://community.logos.com/forums/t/223736.aspx
Thanks Andrew! I switched to the default channel and it's working as expected now. Looks like I need to stay out of the beta channel for now. :-)
0 -
Mark Allison said:
It works in the full search panel. I think the issue was (as Jonathan pointed out) that I'm on the beta channel and it's a bug in the beta.
If it's a bug in the beta, then we would like to fix it. However, I can't recreate your bug report, and I would like more information so that I can.
Mark Allison said:As you can see, there's not even a way to change keyboards in the beta.
I believe this will be fixed in an upcoming version.
Andrew Batishko | Logos software developer
0 -
Mark Allison said:
I switched to the default channel and it's working as expected now.
Note that switching the channel doesn't put you back on the stable version. This just means you won't get further program updates until a new version is released to stable. If you check your About panel, you are probably still running the beta version.
Andrew Batishko | Logos software developer
0 -
Andrew Batishko said:Mark Allison said:
I switched to the default channel and it's working as expected now.
Note that switching the channel doesn't put you back on the stable version. This just means you won't get further program updates until a new version is released to stable. If you check your About panel, you are probably still running the beta version.
I'm back to having the original toolbar. It says I'm at 36.0.727
0 -
Mark Allison said:
I'm back to having the original toolbar. It says I'm at 36.0.727
Yes, that's the beta version. Because the new toolbar will be in beta testing across multiple six week beta cycles, it currently leverages the current channel to determine whether or not it should be enabled.
Andrew Batishko | Logos software developer
0 -
Andrew Batishko said:Mark Allison said:
I'm back to having the original toolbar. It says I'm at 36.0.727
Yes, that's the beta version. Because the new toolbar will be in beta testing across multiple six week beta cycles, it currently leverages the current channel to determine whether or not it should be enabled.
That makes sense. Thanks for the info Andrew!
0