GenoPro Home

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

GenoPro Support Forum

Home Search Tags Who's On

Edit Photo

Welcome Guest ( Login | Register )

Recent Posts Popular Topics

Home » GenoPro » GenoPro 2020 Update » "Display order of children does not match their date of birth"

"Display order of children does not match their date of birth"

Click to view RSS...

Rate Topic

Rate Topic

Topic View

Topic Options

Author	Object selected is sometimes misleading
Jakk	Posted Monday, February 1, 2016 - Post #36648
Famous Writer Customers Gamma GenoPro version: 3.0.1.4 Last Login: Wednesday, November 24, 2021 Posts: 249, Visits: 781	And in terms of its stated goal, the Problem Spotter performs excellently, compared to having to hunt through the list views looking at X and Y coordinates to find overlapping individuals, or having to hunt through lists of dates to find inconsistencies or errors. Spending too long looking at lists is what causes computer users to need glasses, or those of us who already have them to need stronger lenses. Looking forward to seeing a beta for GenoProX... whenever you think it's ready; no rush. Getting these list view bugs fixed has been plenty of immediate gratification for me. GenoPro: Best. Genealogy. Software. Ever.
GenoProSupport	Posted Monday, February 1, 2016 - Post #36645
Legendary Master Administrators Moderators Customers Gamma FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1 Last Login: Monday, June 2, 2025 Posts: 4,886, Visits: 22,796	I agree there is room for improvement. The idea of the Problem Spotter in GenoPro 2016 is to detect a problem to bring attention to the user. GenoProX will try to be more accurate at detecting problems and will offer more often a button to fix the problem.
Jakk	Posted Saturday, January 30, 2016 - Post #36627
Famous Writer Customers Gamma GenoPro version: 3.0.1.4 Last Login: Wednesday, November 24, 2021 Posts: 249, Visits: 781	I have noticed that this message tends to select the first child in a family that has this problem, even when the problem can be solved more easily by moving a different child. For example: The real problem here is the fourth child, not the first. Yes, this is a highly simplified example, but even in the case of an extended and complex genogram, it will nearly always be easier to move a single individual and their family branch than to move three family branches (which is required if one starts this fix by moving the person born in 1972 in this example). In the case of a more complex genogram, it may not be immediately obvious to the user which child or children need to move, and having the program highlight the real "problem child" (rather than simply the first child in the out-of-order family) will make the reporting of this problem far easier to identify. Exactly how easy it is to correct is entirely dependent on the complexity of the genogram and where the problem is within it, and there isn't much that can be controlled there except by the user in the original construction of the genogram. Edit: After some further thought on this, obviously, if the child order is completely scrambled, then it won't matter much which child is selected. I would almost suggest having the program select the family line instead of any of the child objects; from there, the user can simply "Select Children" to highlight them all... or maybe having the program select the family line and all related child objects by default is the way to go. Just thought I'd raise those possibilities. GenoPro: Best. Genealogy. Software. Ever. Edited: Sunday, January 31, 2016 by Jakk

Similar Topics

Click to view RSS...

Expand / Collapse

Reading This Topic

Expand / Collapse



Active: 2 - 1 guest, 0 members, 0 anonymous.
No members currently viewing this topic!

Powered By InstantForum.NET 2010-3-x © 2025
Execution: 0.000. 3 queries. Compression Enabled.