Simple Bible searches not possible?

I've tried to do a simple Bible search, for the word "sit" in the book of James. However, I cannot limit the search to that book, unless I save that as a named range. I don't want to save lots of named ranges, as that would clutter up the list of ranges, and make it difficult to find one from the other. Is there no way to just be able to select a range for that search only, and not save it? I know that I can then go back and delete the range, but that seems wrong. I hope I'm missing some tip or trick, but I don't seem to be able to see intuitively what I'm doing wrong.

Any thoughts?

P.S. That search took 57 seconds to do, to return 2 results! I'm
trying to move over from other free software for such simple
operations, but the slow response doesn't encourage me. Surely it
shouldn't take this long for such a simple search?

Find more posts tagged with

Comments

Mark Smith

P.S. That search took 57 seconds to do, to return 2 results! I'm
trying to move over from other free software for such simple
operations, but the slow response doesn't encourage me. Surely it
shouldn't take this long for such a simple search?

You didn't say in how many Bibles or what Bible you searched. I did this search in just the NASB95 and the search clock said 1.02 seconds (Grid view).

However, I cannot limit the search to that book, unless I save that as a named range.

I don't know what drove that design. In L3 you could specify a range without saving it. You could also create a custom range if you wanted to. I think we should be able to select a range without naming it and saving it, and have the option to save it if we want to.

Rosie Perera

You're right, there doesn't appear to be any way to do what you want without saving the named range. But how about if you keep around a range called "Temp," and always use that name for saving a temporary range that you want to search in? You don't need to worry about deleting it after you're done, because there will only be one, so it won't clutter up your ranges. You'll always overwrite it with whatever new temporary range you use.

The search for "sit" in James took about 2 seconds for me, just searching through "Top Bibles"; 15 seconds searching through "All Bibles." That's on an Intel quad-core machine with 8GB RAM, running Vista SP1. Also it was much quicker doing it a second time (even after closing Logos and opening it back up again), so I'm guessing there is some caching going on which makes subsequent searches (even for a different word) faster.

From what I understand, L4 search works differently from L3. It's so much faster to search in L4 that they always search the entire Bible and then filter the results to the range you wanted, whereas before they would actually limit the search to the range from the get-go.

John Duffy

https://community.logos.com/discussion/comment/42474#Comment_42474

You didn't say in how many Bibles or what Bible you searched. I did this search in just the NASB95 and the search clock said 1.02 seconds (Grid view).

I used just one Bible, the NIV, in Verses view. Maybe it was just busy doing something else at the time, as the CPU icon was at 100% all that time. So, I tried it again. It reported 8.21sec to tell me it has done the search, but it took 45 sec in total to display the two verses this time. There was nothing else actively working, although I have a few MS Word documents open as well as Outlook. But that is still too long.

But how about if you keep around a range
called "Temp," and always use that name for saving a temporary range
that you want to search in? You don't need to worry about deleting it
after you're done, because there will only be one, so it won't clutter
up your ranges. You'll always overwrite it with whatever new temporary
range you use.

That's a great workaround - thanks.

Mark Smith

https://community.logos.com/discussion/comment/42480#Comment_42480

It reported 8.21sec to tell me it has done the search, but it took 45 sec in total to display the two verses this time.

Yes it is, esp. the rendering of the results. I have been through similar speed woes beginning with the first Beta. Logos did a lot to improve the speed of searching selections of scripture. It can actually perform a search on an entire Bible faster than on a limited section because it has to do the full search then trow out results (at least that is what it once did).

I've documented the steps I took to get reasonable speed here: http://community.logos.com/forums/t/4318.aspx?PageIndex=6

Unfortunately not everyone can do as I did (or would care to).

John Duffy

https://community.logos.com/discussion/comment/42488#Comment_42488

If I change to Grid mode, it reports taking 1.72sec to search but a total of 11sec to render it on the screen. Aligned is in about half way in between the two.

Everything else is fast, so I'm not persuaded that I should change hardware and buy a new operating system, just to get Logos 4 working better. It seems like a really great piece of software, that is unfortunately still in Beta mode. I'm now not convinced with the reply from Logos on another post (can't remember which) that the new NET software is causing this slowness, and that time and upgrades will be the solution in the long term. It's just not enough in the short term. I trust that they're working on this, and not just holding their breath long enough for people to upgrade hardware so that the problem diminishes. Although it's still usable with some great features over Logos 3.

Allen Browne

https://community.logos.com/discussion/comment/42476#Comment_42476

... But how about if you keep around a range called "Temp," and always use that name for saving a temporary range that you want to search in? You don't need to worry about deleting it after you're done, because there will only be one, so it won't clutter up your ranges. You'll always overwrite it with whatever new temporary range you use.

Actually, this doesn't work. Logos 4 automatically adds a numeric suffix if the range already exists, so you end up with temp2, temp3, etc being saved.

Mark Smith

https://community.logos.com/discussion/comment/42556#Comment_42556

Everything else is fast, so I'm not persuaded that I should change hardware and buy a new operating system, just to get Logos 4 working better.

I can't imagine doing that.

One other thing to check would be your anti-virus software. Some have reported that instructing the AV software to not protect or scan the Logos 4 directory has improved their speed. I did that, but didn't notice much difference.

John Duffy

https://community.logos.com/discussion/comment/42556#Comment_42556

Reluctantly, in frustration, I've had to resort to using free software for these searches, as I just haven't time to wait from 10-60sec each time I do a basic little search.

Mark Smith

https://community.logos.com/discussion/comment/43499#Comment_43499

Reluctantly, in frustration, I've had to resort to using free software for these searches, as I just haven't time to wait from 10-60sec each time I do a basic little search.

I'm really sorry to hear that.