GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 
Selection Behaviour With Undo


https://support.genopro.com/Topic36851.aspx
Print Topic | Close Window

By Jakk - Monday, March 21, 2016
Something that is driving me crazy right now (and has done so several times in the past) is how GenoPro changes the selection with an Undo operation. I can understand removing the parent and child lines from the selection, because they are attached to their respective individuals and family lines regardless of movements made with them. What isn't so clear is why family lines that were not a part of the original selection get selected with the Undo. I understand that they get selected if they were changed by the movement, but this really makes a mess of things when trying to adjust the placement of a large family group, as the work required to ensure that all family lines not originally selected remain unselected often far outweighs the efficiency of moving multiple objects in the first place. If the Y co-ordinate of a family line does not change as the result of a move and only parents or children of it are selected (not both), then the family line should not be selected after the user performs an Undo. I may have commented on this behaviour before, but my searching did not find anything else on the subject.
By GenoProSupport - Wednesday, March 30, 2016
I discovered this bug while rewriting the Undo/Redo for GenoProX.  I will not touch anything regarding the Undo/Redo of GenoPro 2016 because it is a core module affecting almost everything else, however I can confirm you the new GenoProX has a much smarter Undo/Redo.
By Jakk - Wednesday, March 30, 2016
I am very happy to hear this; I can cope with the existing system while waiting for GenoProX knowing that this has been fixed. I'm also happy that the twins object selection bug will be fixed too, as reported in that thread. Speaking of twins (but not at all related to selecting objects and Undo/Redo), I can live with the family line object behaviour when twins are the last children in the family (as shown in the linked post), but I won't tell you not to fix it. BigGrin