|
|
|
Forum Master
 
 
Group: Customers
Last Login: Today @ 5:55:04 PM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,413
|
|
I have recently added twins to a tree and decided to move branches to a separate GenoMap, using 2b12.
In the new Genomap the point where the twins were attached to the family line was not in the correct place, leading to a long jagged line to the right. After moving the join point back to its correct position on the family line, subsequent moves behave correctly.
Is this a result of the way I created twins? Add 2 children to the family bar and then join as twins.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 8:36:29 AM
GenoPro Version: 2.4.0.3
Posts: 3,523,
Visits: 14,877
|
|
When I move the twins, the points where the twins are attached should move with the twins without any artifact. Can you give me a step-by-step case to reproduce the bug.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 5:55:04 PM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,413
|
|
This sounds like a similar problem mentioned under the import/export of Gedcom, where twins are showing the same behaviour.
I have a fairly large tree (c. 1000). I selected a grandfather of twins; select descendents; move to new Genomap.
When the selection appears on the new map, none of the 'vertical' lines appear until the mouse is clicked. At that point they all appear, but the twin diagonals are offset to the right. Moving the whole selection at that point can correct this, as the attachment point of the twins to the horizontal does not move. When the whole selection is then reselected, the twin lines move correctly.
However on an earlier time the twins did not always move cooreectly; it seems as though the connection point is on a different plane and is not selected.
I have just repeated the exercise on another part of the tree and the twin lines move to the left; a third set moved to the right. The only difference I can see is that the left movement came from a selection with a negative xPosition and the other two had a positive xPosition
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 5:55:04 PM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,413
|
|
Dan
Tried again this morning and found where the problem occurs.
Create a family of parents and 3 children. Set two of these as twins. Select a parent and then descendents. Move to another GenoMap (leaving one parent on the original map) and the problem is revealed.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 8:36:29 AM
GenoPro Version: 2.4.0.3
Posts: 3,523,
Visits: 14,877
|
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 8:36:29 AM
GenoPro Version: 2.4.0.3
Posts: 3,523,
Visits: 14,877
|
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 5:55:04 PM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,413
|
|
| As a test of the twin link I created a family with one son and one daughter and linked these as twins. I then clicked on the twin link and in the Properties menu changed the Twin Link to identical. A minor point, but a brother and sister are not identical. If a thing can go wrong, it will go wrong, so can this option be 'greyed out' in such cases?
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 5:55:04 PM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,413
|
|
When selecting a family by using the 'Select Descendent Tree' the twin link is only partly selected. A vertical movement includes the twin link but a horizontal movement does not. At present you have to add the link explicitly to the selection
Version 2.b12g
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 8:36:29 AM
GenoPro Version: 2.4.0.3
Posts: 3,523,
Visits: 14,877
|
|
When selecting a family by using the 'Select Descendent Tree' the twin link is not selected.
Thanks for pointing this bug. In fact, the twin link was not selected at all. I have fixed the bug for the 'Select Descendent Tree', 'Select Direct Descendents', 'Select Ancestor Tree', 'Select Direct Ancenstors', 'Select Entire Tree' and 'Select One Generation'. The fix will be available in Beta 13.
|
|
|
| | |