latest release is cursor greedy!
Hi,
every time a new family is expanded by a user the cursor becomes attached to this point! Moving the mouse even quickly causes entire page to move with the mouse. The only way to get the cursor free is to right click get out of app drop down and then cancel that! Verty frustrating to use the new pedigree page of the moment!
Ongoing problem with page refresh or accidental click on the background cause the entire page to move to the extreme left or right. Thus losing context ! When working to long trees it can take a long time to go back to original person you are working on!
Please add a search for person by name or id on the pedigree page .
Please why are relationships limited to 15 generations please extend this further
項留言
-
I agree the cursor problem needs a fix.
Paul - “Ongoing problem with page refresh or accidental click on the background cause the entire page to move to the extreme left or right.” I also have the problem with the page refresh moving the entire page back to the left. However, clicking on the background isn’t causing the entire page to move.
0 -
if you mis click the very small icon on top right it causes the person details to be displayed and a refresh. Then the entire page goes to extreme left or right and usually the opposite side of where you want to be! With large trees it can take up 10 minutes to find where you were.
Need a search by name or id on the pedigree tree!
0 -
@PaulHarrison61: You unfortunately used this discussion to firehose all of your concerns at once, so here are all of your answers, all at once. We have just released a fix to help mitigate mouse-stealing behavior. Clicking elements on the pedigree should no longer cause an unnecessary re-center. If you are experiencing a different issue, please add reproducible steps. Keeping your scroll location across page refreshes or having a "go to end" button is a bit more complicated, but we are working on a solution. In the interim, if you are constantly working dozens of generations back, I strongly recommend updating your Family Tree Starting Person here: https://www.familysearch.org/identity/settings/account to be someone closer to the area of the tree you are actively working in. Adding local tree search has been an idea considered for some time, now, but has never received enough attention to be developed--but that may change with this year's initiatives. Any database system has hard limits, and if you consider that a fully-populated family tree will consist of 2^n individuals, where n is the number of generations, two to the sixteenth is 65,536. Then consider that from any one of those ancestors, we also have to search back down through any descendants they may have, that base number is modified by a linear growth function, where we have to search through hundreds of thousands of current relationships to determine if there is a relationship. We had to draw the line somewhere before running a relationship check takes down the entire system.
0 -
Thank you cliff. My intent was not to firehose. My apologies if you got that impression.
I have over 35000 people in my family tree over 30 generations and to lose context in a big issue. Statically setting a new start point each time a different branch is being worked is not viable but a good try as work about .
I do understand the exponential growth of the search of a db . I am interested also how the app allow for 2 sisters marrying 2 brothers relationships and say 3rd cousins marrying without getting its knickers in a twist?
Keep your good work up please and have a good day
1 -
Sorry for being snippy, Paul. There is just a lot going on, right now, and while we love helping our patrons in the community, the less targeted a discussion is, (i.e. the more topics it addresses), the less likely it is that the conversation details will be seen by others who have the same questions. And the more likely it is that we will have to repeat the entire conversation, again.
As far as your last question, that is one of the caveats of the relationship search system. Whatever relationship path calculates fastest is the one that is returned, which is not necessarily the shortest path (this is one of those things to keep relationship finding from breaking the entire system, as the other search branches are terminated as soon as a path is found). I wish this disclaimer were a bit more prominent in the feature, but there you go.
1 -
Update: The stick cursor problems were fixed a long time ago, and Paul's comment of keeping you place in the pedigree after refresh or leaving the page and coming back is currently being worked on.
0
