|
By Jakk - Tuesday, September 29, 2015
|
|
I don't know why it took me so long to notice this. When using "match each word" or "fuzzy match" the program stops at the first match found in a record, even if there is a closer match later in the record. This may have already been reported and fixed in the new version, which I haven't tried yet; this is my first visit back to the forums in a few months, and I'm rather excited about there being a new version to play with. Thanks!
|
|
By GenoProSupport - Tuesday, September 29, 2015
|
|
This is the first time I hear about this bug. The search algorithm was written as follows: every object (individual, family, picture) is queried if it contains data matching the search criteria (text, uppercase, each word, fuzzy match). If so, the object is added to a list which is then displayed in the Table Layout.
|
|
By Jakk - Saturday, October 10, 2015
|
|
Interesting that this hasn't been reported before. I have another search bug that might be new, too... and it might be more of a system bug than a bug in GenoPro... but I'm trying to find a name in a medium-sized (for me; about 2000 individuals) genogram using the search function, and it is repeatedly returning "not found"... despite the fact that I can find four occurrences of that name, spelled exactly the same way as my search term, when I do a list-view lookup. Is the program actually trying to drive me insane, or is this a software bug, or is it possibly a system issue (maybe a memory problem)? The name has accent marks in it, and I've tried fuzzy match, turning off accent matches, and spelling the search term with the correct accent marks.
|
|
By appleshaw - Sunday, October 11, 2015
|
One or more of the names may have a space at the end. This will cause problems with the search which normally looks at Display name. I tried an unusual name which displays as "Jabez Hackethal ". You can see there are two spaces between forename and surname and a space at the end.
Probable cure is for GenoPro to clean spaces at the end of a name
|
|
By Jakk - Wednesday, October 28, 2015
|
After getting sidetracked by other GenoPro projects and things unrelated to genealogy, I finally got back to this, and it seems to have been a temporary bug, probably related to memory issues on my system. I tried the same search in the same file, the only change being that it was the first thing I did after starting GenoPro right after starting up the computer, and the search worked fine. Good to know that it's my computer, not the software, that's trying to drive me insane, because I love the software; I can always get a new computer. 
|
|
By GenoProSupport - Wednesday, October 28, 2015
|
|
Let me know if there is a bug in GenoPro.
|
|