No longer able to move a record up/down in Source Linker
Sometimes a family has more than one child with the same name. Source Linker picks one if it exists to attach a new source. You used to be able to drag the entry up or down to align with correct child (or identify as a new child).
Answers
-
You can still move the entry but now you have to click about where the name is. It used to be done by clicking anywhere in the box.
0 -
Best way to move the entry is to click and hold on the hidden arrows. Then it moves just fine. What I didn't know until I went to take an image to show this, is that they have recently moved the arrows:
I suspect they found that new users could never find the arrows and that it was more natural to try to move the entry by clicking and dragging on the name. The target area for triggering the arrows is also much larger now. You used to have to be pretty much right over them. Now they appear and you can click and drag the entry where ever you are in the target area outlined below:
2 -
@Gordon Collett said…
"… Best way to move the entry is to click and hold on the hidden arrows. ..."
It is always possible that I am misunderstanding what Gordon is explaining here, and I can't cross check on my PC right now, but something seems a little odd about a User Interface which asks people to click and hold hidden objects.
"... I suspect they found that new users could never find the arrows ...".
Sarcasm alert... I wonder why new users could never find the hidden arrows?
Having said all that, I don't remember any issues that I ever had with moving entries, so maybe I naturally grabbed the entry at the point where it was adjacent to the existing family members. Which now makes me worried that I won't find the (invisible) arrows under the new regime because I'll be clicking at the wrong end. 😕 At least, if I remember this, then I am forewarned, thanks to Gordon.
1 -
@Adrian Bruce1 , if you have never had any trouble just dragging the box and, with re-reading his post, @MDNash79 has always just "clicked anywhere in the box," this raises the distinct possibility that I have been deceiving myself for years in thinking I had to aim right at the arrows. This also brings up the question as to whether an engineer was adjusting some formatting parameters, accidentally cut the length of the target area in half, and this is actually a new bug rather than a modification of the feature.
1