Jerry Bryan

The title says it all.

RM7 does not place multiple spouses for the same person in marriage date order by default. Instead, you sometimes have to Edit>Rearrange>Spouses to coerce the spouses into the correct order. Doing so fixes the order for things like Descendant View and narrative reports. But doing so does not fix the order for Search>Family List. It can be very confusing, and there does not seem to be an Edit>Rearrange way or any other way to fix it.

I don't expect or wish for this to be fixed in RM7,but perhaps it can be fixed in RM8 - maybe in RM8.1 if fixing it in RM8.0 would delay RM8.0 getting out the door.

Jerry

Multiple marriages to the same spouse can occur for a variety of reasons. For example, you might record a civil marriage and a religious marriage for the same couple that take place on different days. Or a couple can marry, divorce, and remarry.

In these situations, Search>Family List does not show the multiple marriages correctly. It does show the couple twice, which is correct. But it shows the same marriage date both times rather than one of the marriage dates the first time the couple is listed and the other marriage date the other time the couple is listed.

I don't expect or wish for this to be fixed in RM7,but perhaps it can be fixed in RM8 - maybe in RM8.1 if fixing it in RM8.0 would delay RM8.0 getting out the door.

Jerry

With RM's interface to FamilySearch, each matched person in RM has a FamilySearch icon that can be clicked to go directly to the matching person in FamilySearch Family Tree. Not everybody in your RM database is matched to a person in FamilySearch Family Tree but each matched person is identified with this very useful icon.

It occurs to me that TreeShare needs the same kind of icon for each person who is "matched" to ancestry. TreeShare does not use the same "matched" terminology as does RM's FamilySearch interface, but it's the same concept. When you first download a new ancestry tree to a new RM database or vice versa, each person in your RM database is "matched" behind the scenes to a person in the connected ancestry tree. After an initial TreeShare, you get "unmatched" people between RM only as the result of additions or deletions or merges. So it sure would be handy to go straight from an RM person to the corresponding ancestry person just like you can with FamilySearch.

What you have to do instead is to open TreeShare and then navigate to the same person in the TreeShare screen. Doing so can be a major pain. It's a major pain anyway, but more and more I'm finding that my RM locks up for 20 or 30 or 40 seconds if I type in a name on the TreeShare screen to navigate to a person. If I'm lucky enough to have an ancestry WebHint, I can click on the light bulb and get the to "matching" person right away. But often I don't have an ancestry WebHint even though there are shaky leaves for the person on ancestry.

My computer runs Windows 10 with 16GB memory, a quad core processor, and a solid state disk. For most tasks, it runs very crisply and fast, so it should have more than sufficient horsepower to run TreeShare effectively. I don't know what's going on in RM when it seems to get locked up when I type a name into TreeShare, but Windows Task Manager says that it is consuming huge amounts of CPU time. It doesn't appear to be waiting for ancestry to respond.

We don't know yet how many of the various TreeShare problems are fixed in RM8, and for all we know the TreeShare feature I'm requesting might exist in RM8. But if not, perhaps it could be added after RM8 is out the door and is stable.

Jerry

I didn't know whether to post this under Issues or under FamilySearch, but it seems to me to be more of an RM issue than a FamilySearch issue, so I am posting here.

I have had several instances lately where RM7 locks up when I click on the FamilySearch icon to go look at a matched person in FamilySearch. The process of getting into FamilySearch is successful. I look at the person in FamilySearch, make no changes, and close the browser window. RM is now locked up. RM is not in a loop because it is taking no CPU cycles. But it is completely unresponsive. The only way out is to use Task Manager to kill RM and then to restart RM.

It's hard to know how to get any diagnostic information to help identify the cause of the problem. And I don't expect or want any effort to go into solving this in RM7. I do hope that RM8 locks up less and has fewer invalid address kinds of errors than RM7. We shall see. With its less modal design, RM8 is going to have to be very careful about such issues. I'm pretty convinced that a lot of RM7's problems in this area have to do with background tasks that are performed in threads that are not being properly synchronized. That's why I think RM8 will have to be especially careful about proper synchronization between its non-modal windows.

Jerry

This is just an alert for RM users, due to how critical the interaction between RM and Dropbox can be. I woke up this morning to a new version of Dropbox that appears to have removed the Sync Pause/Resume option. At least it's gone on one of my two computers (the one where I run RM most of the time), and it's still there on my other computer. I suspect it's only still there on the second computer because it hasn't updated yet to the most recent version of Dropbox.

I spent about two hours just now chatting with the Dropbox HelpDesk. They hadn't gotten the memo, and they were convinced for a long time that I just wasn't looking in the right place for the Pause/Resume option. I finally persuaded them with a 15 second long screencast of the problem. Static screen captures for some reason wouldn't catch the problem. They are going to escalate the problem to the developers. I don't have high hopes for a positive response from the developers.

In the meantime, the only solutions seems to be to Quit the Dropbox product completely while using RM and then to restart Dropbox after finishing with RM, or to de-install Dropbox and install a competing product in its place. Well, another solution would be to move your RM database completely outside of your Dropbox folder, which after all is the official RM recommendation anyway. I would be curious to see if there are any other RM users who have been bitten by this problem. Surely I can't be the only one.

Jerry