Release Notes for rootstrust, Version 0.9 beta, Build 378
I. Changes in Support of GEDCOM Import.
A. Place Preprocessor. The GEDCOM Import Wizard has been outfitted with the Place Preprocessor that I have been promising to deliver. It works in a manner similar to the Place Group Editor but offers you greater flexibility in that it allows you to convert non-place data to notes (some programs treat the Place field as a comments field allowing you to store notes or source citations in it). The Place Preprocessor does the following:
B. Imported Value field removed. Since the Place Preprocessor has been implemented, there is no longer a need for the Imported Value field in the Place Detail form and the Place View. The space used by that fields and its label has been returned to the Notes field from which it was borrowed.
C. Progress bar change. A Close button was added to the GEDCOM import progress form. The button does not appear until the import process is complete.
D. “Pseudo Person” bug fixed. A bug was corrected that was causing Persons imported from a GEDCOM file to be classified as “pseudo persons” if their names start with a non-alphabetic character, even if the GEDCOM file came from a program other than The Master Genealogist.
E. Additional Legacy support. Support was added for the following Legacy non-standard tags:
F. Custom Event types. The number of entries on the “Custom” tab of the “Select Event Type” dialog was limited to 30. Since one of the beta testers has over 70 custom Event types, that restriction has been lifted.
G. GEDCOM Import log changes. The GEDCOM Import log now lists the options that you selected in the GEDCOM Import Wizard. In addition it enumerates all custom Event types defined in the GEDCOM file.
H. Additional Family Tree Maker support. Support for the non-standard Family Tree Maker _SCHEMA tag has been added. This tag provides an alternate way of defining custom Events/Facts that rootstrust had not recognized until now.
II. Changes in Support of Large Databases. Extensive changes were made to be provide greater user friendliness to users who have large databases (> 50,000 Persons). Some operations that appear to be instantaneous for small or medium size databases can take up to ten seconds to complete for large databases.
1. Person Index optimization. The index is no longer reloaded after adding a Person to or deleting a Person from the database. The index is also not reloaded when you select a different filter from the combo box (ex. “All Persons” to “All Ancestors”), the non-applicable index entries are hidden so that they can be reused without having to access the database. If you have made a lot of additions and/or deletions and need to refresh the index, you can click on the Refresh button located to the right of the index filter combo box.
2. Form “Add Person” optimization. This form (used to add a spouse or parent) has an option that allows you to select a Person from a list. The list is essentially identical to the Person Index. So now the form copies the contents of the Person Index into its list rather than creating a new list from the database. This speed up the displaying of the list dramatically.
3. Form “Select a known Person” optimization. This form (used by the Relationship Calculator, GEDCOM Export, adding a secondary Person to an Event, etc.) was modified that same way as form “add person” was modified.
4. Optimization of maintenance commands. The MaintenanceàUpdate menu commands “Reset all Ancestor flags” and “Propagate Ancestor flag to ancestors of root Person” have been optimized to execute in a fraction of the time that they were taking in earlier builds.
5. Optional report output restriction. The output of report types Ahnentafel, Family Tree Chart and Family Group Sheet can now be restricted by maximum number of generations.
III. Other Changes.
1. Place merge, a capability that I promised in the Release Notes of Build 374, has finally been implemented. Sometimes we inadvertently create multiple Place objects for the same geopolitical entity through misspellings or by specifying a different number of levels (one with county and another without). With the Merge capability you can combine such semi-duplicate entries. You will find a Merge button on the Place View to the left of the Group Edit button.
2. Enhanced Place Group Editor. The Place Preprocessor shares much of the functionality of the Place Group Editor which is accessible from the Place View. New features incorporated into the Preprocessor that were missing from the Place Group Editor have been added to the Place Group Editor:
3. Sort Sequence. The Person Index, Family Index and Place Index are displayed in sorted order. The default collating or sort sequence is “English, United States”. This setting will work for most English-speaking countries and many other countries as well. However, if you live in a Scandinavian country, you probably will want to change the setting so that the letters Ä, Å, Æ, Ö and Ø are displayed after Z. The change can be made on the User Interface tab of the Preferences form.
4. New date format. “31 Jan 1900” was added to the data format combo box on the User Interface tab of the Preferences form.
5. Date format bug fixed. The output of the “31 JUN 1900” date format was corrected to use the 3-character month designation even when the data is composed of only the month and the year, thus generating the date “JUN 1900” rather than “JUNE 1900”.
6. Upper case and title case conversion. All text fields on the Place Detail form, Place View and Place Merge form have been modified to respond to a right mouse button click by displaying a popup menu. The menu has two commands: “Upper case” and “Title case” (each word starts with an upper case letter followed by all lower case).
7. Relationship Calculator bug fixed. In the process of converting from two sexes to three we broke the relationship calculator. This has been fixed.
8. More temporarily expandable text fields. All text fields on the Database tab of the Preferences form are now temporarily expandable. When one of these fields has the mouse focus and you right click the mouse, the field's width increases to fill the width of the host panel making it wide enough to accommodate very long text values. When you release the mouse button, the field returns to its normal width.
9. Root Family selection on the Database tab of the Preferences dialog was not working properly from two aspects:
Both of these errors have been corrected. And please note that to select a family via the wife’s name you must:
IV. What’s next? I will immediately start working on the interface with FamilySearch.org. I do not know at this time when this feature will be available in rootstrust, since, in addition to the software that must be developed, certification of rootstrust by FamilySearch.org is required. If I am prevented from offering this feature due to the necessity to wait for certification, I will work on other enhancements such as:
1. A descendant view
2. Professional quality source citations
3. Help creating a cameo photo image for the Person View. Presently you must crop and size these images manually prior to importing them. I plan to provide a capability where you can select a square section of a photographic image that will be extracted, sized to 150 x 150 pixels, stored in the appropriate File Cabinet and installed in the cameo photo panel for the current Person.