Switching current spouse in new Source Linker?
The original Source Linker had a little grey arrow that let you switch which spouse of the focus person was showing on the Family Tree side of the screen (the right side). I don't see that now in the new Source Linker. I had a case where a record had Wilber and his wife Marjorie showing on the left, and the correct Wilber and a different wife showing on the right. The Family Tree person did indeed have a wife corresponding to Marjorie, but I didn't see any way to switch to that being the currently-displayed spouse like we used to be able to do.
Yes, I could switch to Marjorie being the focus person on the left and then do the same on the right, in order to get the two Marjories to be displayed at the same time so that I could link them. But that is several more steps and seems harder for users to figure out. I also suspect there are cases where this still isn't sufficient for handling things like adding new children from the record to the right couple in Family Tree, especially if both spouses have multiple spouses. You're at the mercy of Source Linker happening to pick the right spouse to show on the right.
(Incidentally, the idea and gif for the grey spouse-selector arrow were copied from the Landscape view of Family Tree, which users were already familiar with. I just looked and it appears that the grey arrow disappeared from there, too, making it impossible to select a different spouse there as well, unless I'm missing something).
의견
-
For me, the new Source Linker has a down arrow and a (relatively) large "CHANGE SPOUSE" label at the bottom of the spouse's box. Is that improvement missing for you? (The old arrow was so hard to find and identify, I remember I actually posted a question about it here in Community. I had tried and failed to find the magic pixel.)
On the Landscape view, the arrow has been replaced with an enigmatic two-people icon to the right of the spouse that's currently showing.
0 -
Thanks for pointing both of those things out. Somehow I wasn't seeing that before, but it's obvious now.
0