PDA

View Full Version : Check Box Search Bug



Adelphos
04-15-2009, 07:13 PM
I make SCR my search version. I type .pistoj on the CL. It gives me 33 verses. I leave them all checked.

I now type KJV on the CL to make that my search version. Then I Limit Search To Checked Verses via the context menu.

I now type .faithful on the CL. It returns 0 hits, which is of course erroneous. I am using the latest update.

MBushell
04-15-2009, 08:38 PM
Scott,
Please report bugs via the procedure at http://www.bibleworks.com/support.html. That's not really the purpose of the forum. Bugs reported here may or may not be seen by anyone at BibleWorks. Staff looks in on the forum occasionally but there is no guarantee of that and no guarantee that bugs reported here will be entered into the bug queue. The forum is mainly intended as a means for users to interact with each other. If frequent staff interaction results in large scale bypassing of primary reporting channels, BibleWorks staff will have to completely avoid the forums, and none of us want that. The reason we do it this way is for efficiency. BibleWorks tech support staff are trained to deal with bugs and track them. They can't do their job if they are not the primary reporting venue.
Thanks,
Mike

Adelphos
04-15-2009, 10:07 PM
Scott,
Please report bugs via the procedure at http://www.bibleworks.com/support.html.

Okay, but the purpose of the post was to see if anyone else could reproduce the problem. Although I find this problem on both of my computers, I share files with both computers so I wanted to make sure that it's not specific to me. The purpose of the post was to see if anyone could reproduce it, and then, if so, to then report it via Support.

Mark Eddy
04-15-2009, 10:54 PM
Scott,
Yes, I can reproduce your problem. Also, if you click on the arrow to the right of the command line and click on the previous SCR search from the drop-down list, that original search comes up with zero hits as well.
Mark Eddy

Adelphos
04-15-2009, 10:56 PM
Scott,
Yes, I can reproduce your problem. Also, if you click on the arrow to the right of the command line and click on the previous SCR search from the drop-down list, that original search comes up with zero hits as well.
Mark Eddy

Thanks, Mark. I sent the report to CS.

DavidR
04-16-2009, 02:58 PM
I find the same thing happens using first BGT and then NRS. In fact when I do what Mark mentions and click on the arrow to go to the previous BGT search, BW crashes altogether.

I also find that even if I stay with the original search version and select "Limit Search To Checked Verses," it returns zero results, when I know that there should be one or more.

Makes me wonder what the "Limit Search To Checked Verses" option is actually for.

MBushell
04-16-2009, 10:26 PM
Okay, but the purpose of the post was to see if anyone else could reproduce the problem. Although I find this problem on both of my computers, I share files with both computers so I wanted to make sure that it's not specific to me. The purpose of the post was to see if anyone could reproduce it, and then, if so, to then report it via Support.

I understand Scott. We have to stipulate occasionally that the official channel for bug reports is through the web site and company e-mail addresses. You were sort of in the wrong place at the wrong time and got hit by the bullet that gets fired occasionally :-)

The limit search to checked verses was intended to be used only with the original search version. That's why it doesn't work. It's not really a bug. It's just using a feature beyond the intended range of use. We can make it work in the manner you are using it here, but it gets very very complicated very quickly. Just think about it. The old verse list must first be remapped to the new version. Then the search has to be done and either (1) convert the new hits to the old version or (2) convert the old list to the new version. Remember verse numbers may differ between versions. The conversion back and forth can actually remove verses that you may want. In general if you convert one version to another version and back you won't get all the verses back because some versions have verses that others don't.

The best way to avoid all this is to convert the verse list to the second version (using the command line "convert" command. Then do the second search. That way you see the intermediate steps and are less likely to be surprised.

However, if people want to do what you are suggesting, the capability can certainly be added and I'll stick it on my list. Just be aware of the possible pitfallls and confusion.

Mike

MGVH
04-16-2009, 10:37 PM
I'm not sure what Mike means by "convert" on the command line...

I do it by left click on green bar just below command law and choose bottom option to Synchronize Results List

Adelphos
04-16-2009, 10:57 PM
I understand Scott. We have to stipulate occasionally that the official channel for bug reports is through the web site and company e-mail addresses. You were sort of in the wrong place at the wrong time and got hit by the bullet that gets fired occasionally :-)

I'm pretty used to bullets, whether intentional or not. :cool:



The limit search to checked verses was intended to be used only with the original search version.

Okay then, here's the problem, I think. I got an email from CS on BibleWorks Classroom Tips, and this very example is one of the two given. The exercise can be found here --

http://www.bibleworks.com/classroom/2_08/

I didn't follow the instructions properly, i.e., the ONE thing I didn't do was Synchronize the Results list. When I do that, it works perfectly.

In short, it's not a bug, and I don't think it needs to be changed. All one must do is synchronize.

In the future, I'll leave the word "bug" out of the thread header and also ask specifically if anyone can reproduce it.

MBushell
04-16-2009, 11:20 PM
Okay then, here's the problem, I think. I got an email from CS on BibleWorks Classroom Tips, and this very example is one of the two given. The exercise can be found here --


This is an example of the guys in the office going beyond the programmers. I suppose it is a reasonable extension but not one really intended. I can make it work as you describe, but it will be a bit of work because of the verse mismatches between version. I assume this is what you want:

1. Do a search and uncheck some verses
2. change versions
3. do another search which will convert the verse list behind the scenes to the new version, do the search and keep only verses that map to one of the verses in the original list
4. convert that list back to the original search version and replace the original list.

Right? Yuk.

Adelphos
04-16-2009, 11:23 PM
I can make it work as you describe, but it will be a bit of work because of the verse mismatches between version.

Mike, I REALLY do NOT think you need to change it. I did NOT know about the "Sychronize Results List" option, and this handles the whole thing perfectly.

I would leave it alone.

Adelphos
04-16-2009, 11:38 PM
This is a much more flexible tool than I realized. This is very basic, but note...

1. Search version SCR. Search for pistos, returns 33 verses.
2. Switch to KJV.
3. Click on KJV in the green box and select Synchronize Results List.
4. R-click on CL and choose Checkbox Search Filter | Limit Search To Checked Boxes.

5. Type .!faithful

Viola!

A very basic demo of the flexibility with the new Checkbox feature. Don't forget to change your filter back to encompass everything.

DavidR
04-17-2009, 10:18 PM
The limit search to checked verses was intended to be used only with the original search version.

Mike, I can't get it to work that way either. I hate to ask for such hand-holding, but I just don't get how this is supposed to work. Here's what I do:

I search in BGM (with a limit set for NT) for, say, koinwnia. There are 17 verses returned. I leave them all checked, and I select "Limit search to checked verses." I do a new search, still in BGM, for pneuma. I (sometimes) get a little message at the bottom of the window that says, "Merging Word List ...", and that's all that happens. No results appear at all. Sometimes the program crashes entirely. Unchecking some of the verses produces the same result.

What am I missing?

Mark Eddy
04-18-2009, 01:13 AM
David,
I did the exact steps which you described, and I get two hits, 2Co 13:13 and Phi 2:1. Try shutting down BW and reopening it and doing your searches again. You may have done something which you do not remember doing, and that may be messing things up.
Mark Eddy

MBushell
04-18-2009, 10:49 AM
I just posted a new exe that should fix the problems with this option. It should not crash and it should also remap the verses if you change versions before doing the limited search. But the verse list will also change to the new version.

MGVH
04-18-2009, 11:35 AM
Using 8.0.008q.1 on WinXP SP3

I also tried following DavidR's example, and it got hung up w/ Merging Word List. If I then try to do anything else, it crashes the program.

BUT
I may have some clue as to why it is doing this.
If I use BGM and set my search limits to just the NT, go through the steps noted, it crashes everytime.
IF, instead I start without any search limit (or use the BNM), it works perfectly and quickly.
>>> It appears that you can't have any other search limit set in order to use the Checked Results search parameter.

NOTE: You can run the initial search with limits set BUT before you run the Checked Results search, you need to remove those limits.

Greg Ward
04-19-2009, 07:47 AM
I just posted a new exe ...
A Saturday morning fix--you gotta' appreciate those hardworking BW programmers. They sure do add tools to our toolboxes.:)

DavidR
04-19-2009, 11:37 AM
OK, it's working now! I upgraded to v. 008q.1. Using BGM, I can get it to work as Mark describes. I can also follow Scott's example using SCR, then switching to KJV. When I do the same thing using first BGT and then NRS, it also works.

In fact, even if I put a range limit (e.g., NT) on the original search, the "Limit search to checked verses" option will still work if I remove the range limit before applying it.

Thanks, everyone, for your help. I can see that this will be a useful tool in real-world work.