Jump to content

JohnR

Senior Members
  • Content count

    205
  • Joined

  • Last visited

Posts posted by JohnR


  1. This is a known problem, Jack, and it happened to me too yesterday. I was able to close TMG using 'Check for an Update' on the Help menu - which allows TMG to close its open files and shut down normally. If 'Center the Current Window' on the Window menu is not dimmed too when this happens, sometimes selecting that will fix the problem.

     

    You might try the menu Add Person instead of the toolbar and see if it is better.

     

    Virginia

     

    Add person from the menu doesn't work for me either. Contemplating adding my demise to my TMG data :wacko:


  2. Today I noticed that reports, of several types, do not start with the person's name where the first tag is a custom tag. This is a new problem. I have been using this custom tag for several years with no difficulty.

     

    I have a custom tag "Who is" which is designed to appear after the person's name and before his date of birth. It is date sorted to be the fist tag in the list; its sentence contains just a memo and location so that the result can read "draper of Boston" now the resulting reports start Draper of Boston. He was born 1 Jan 1111 instead of John Doe. Draper of Boston. He was born 1 Jan 1111.

     

    What have I done to upset the system?

     

    John


  3. Has anyone written a macro, or is there a tool to delete carriage returns and reform lines of copied text in memos?

     

    I copy/paste unformatted text to a memo field and currently go: End - Delete - Spacebar to reform text. This is boring when I have just plagiarised a large amount of text.

     

    Is there anything to speed-up this process?

     

    John


  4. Leading zeros are stripped from each date part in report output if the option to retain leading leading zeros is not selected. However, there is a limitation... only one leading zero is stripped from each date part. I tested several date formats but not all. You didn't say which format you are using.

     

    So... 01-01-0975 would be output as 1-1-975. However, 01-01-0001 would be output as 1-1-001.

     

    Not an issue that I recall coming up but I'd guess that the failure to strip all leading zeros from a year is a bug.

     

    I am using dd Mmmy yyyy format. However this "bug" seems to be limited to "between" dates. I am using a birth tag "between 0970 and 0975" and this is producing the report output "b. between 0970 and 0975" I haven't tried it with other conditionals.

     

    John


  5. The Name tag suffix field was, I presume, designed for the use of "Junior" "III" etc. Unfortunately I have also used it for decorations, degrees and other abbreviations that a person is entitled to use after their name. This results in a tortuously long name appearing in reports when the personal pronoun is not called for.

    e.g. Dr. Sir John Doe, K.G., V.C., D.S.O., D.C.L., M.A. is fine for the first name tag in a paragraph but its boring when it occurs several times. Is there a way of getting a report to just use say, First and Surname when the "full name" is used in a report after the first occurrence?

     

    John


  6. John, what do you mean by "null sentences?" The default sentence for that tag is:

     

    <As of [D],>[PP] married name was [N] <[M]>

     

    If you are using the UK version, there is no default sentence in English (UK), so the default sentence in English (US) is used - that's the one above.

     

    If you have deleted the active sentence for that tag type, and that tag type is included in the report, you will still get a period produced by that tag. Empty sentences still print, but produce only the period. That would agree with the results you describe.

     

    To avoid the period you can:

     

    1) Exclude the tag from the report, by using Selected tags and then not selecting this tag type, or

     

    2) Change the sentence to an exclusion marker (a hyphen).

     

    That seems to have solved the problem. 3 years of the occasional whinge to Dorothy and it was that simple. Thank you.


  7. What tags lie between the birth and marriage tag in her person view?

     

    And what tags lie between the marriage tag and the one producing the last sentence in her person view?

     

    Assuming there are tags there, what are their sentences, and what are the contents of the fields referenced in the sentences?

     

    The default Name-Marr in both cases with null sentences (as they came out of the packet all those years ago!)


  8. Thanks for the explanation.

     

    If I were to implement something—and this is not a promise or even an indication that I will—I would not use flags. I think it's more appropriate to use Surety values on the relationship tags to indicate which type of line should be used, given that Surety is intended to indicate confidence in an assertion.

     

    Should something like this happen then just possibly I might have to start using Surety values but then I am sure that there would be a TMG Tool to enter a global surety value of greater than the value that triggers dotted or dashed lines where the field is null :D


  9. Can you reproduce it?

     

    Yes

    In an individual narrative (but not limited to this report - its just easier to find as an example)

     

    Emma Duncan Crooker was born on 17 Sep 1836 in Bath, Maine. . She married Hon. Arthur Sewell, son of William Dunning Sewell and

     

    Standard sentence = [P] was born <[D]> <in [L]> <[M]> in UK English

     

    and another

     

    Hadeguisa (Unknown) married Robert Marmion Sieur de Fontenay. . She recorded as a widow and a nun at Caen in 1101.

     

    [P] married [PO] <[PARO]> <[D]> <in [L]> <[M]>


  10. I am not familiar with the "convention of dashed or dotted lines in pedigrees" so please explain what you mean. Under what circumstances would SS produce dashed or dotted lines rather than solid lines?

     

     

    In pedigrees where the line is dubious. In the specific area that I am working on there are direct ancestors to a certain point, say 1170 and then the probable line is to someone named in the Survey in 1087 who was the landholder. The convention of dashed lines was used by antiquarians to indicate that the pedigree can be proved to continue through the tenancy rather than by blood. The dotted line seems to have been used when they were on even shakier ground.

     

    What I envisage in simple terms would be that all "graphical" lines running from a person with Flag type A would be ----- and all from Flag Type B ..........

     

    John


  11. You don't need to end memos with a period - TMG adds one if none exits at the end of the sentence. But it shouldn't allow multiple periods, and I'm unable to replicate that. My guess is that you have one or more tags included in the report that have no output themselves and are just contributing their final periods. I'd suggest comparing the output in the report with the list of tags in the Person View to see if any tags fail to produce text.

     

    Terry, I am certain that this double/treble period is a bug - I have reported it several times over the last two or three years


  12. Can I add an "I wish" to both TMG V7.1 and SS2.5 ?

     

    I am presently working with medieval records and families and some ancestors do appear to run with the land tenures rather than gentically. I would like to be able to reproduce the convention of dashed or dotted lines in pedigrees both in print-outs to send to my editor (human) and to my website.

     

    A dotted/dashed pedigree line might also be helpful to those people who are constructing pedigrees of doubtful merit. I presently use a flag for these but that only helps when I am viewing in colour.

     

    John


  13. Surnames can be displayed in caps or exactly as you enter them.

     

    Preferences / Current Project Options / General / 'Display surname is CAPS'

     

    This option is selected by default but you can unselect it to display surnames as you enter them.

     

    Thanks Jim, but I don't think this solves my problem of viewing REES AP REES as REES ap REES, what I was hoping for was something like say: REES [LCASE:]ap[:LCASE]REES


  14. I would like to force some words in a surname into lower case

     

    I have for instance: Given Name = Anharad Pre-surname = ferch Surname = DAVID AP LLEWELYN AP DAVID AP GRONWY and I would like the AP to appear as ap because it makes it easier to read.

    I know I could simply make Anharad the daughter of David and David the son of Llewelyn but then in the pick list I run into the difficulty of distinguishing one Anharad ferch David from another.

     

    Suggestions please ?

     

    John ap Rees


  15. Did you try the menu as opposed to the toolbar button?

    Just coming to post about that. I can add wife, brother sister, etc from the drop-down menu (least it calls the right boxes) but the chap with the + sign at the top of the drop down menu (add person) causes it to freeze, as does clicking on his twin brother on the menu bar below.

     

    John


  16. Try going to Menu>Windows> and select "Center Current Window"...sometimes the Add Person Window opens behind other windows and it appears that TMG is frozen...if that's the case "Center Current Window" will bring it to the front and you can proceed with no problems...

     

    Thanks, but its not that. The menu bar greys out when she freezes and its Alt, Ctl, Del to get going again.

    John


  17. Today TMG 6.12 (UK) took it into its head to freeze when I clicked on Add New Person.

    Maintenance run. TMG reloaded. TMG removed and root directory deleted. TMG re-installed from fresh download. Windows and TMG started in safe mode and still froze on Add New Person (even though it was a different person by now!).

     

    TMG running under XP sp2 on 2.80 GHz 1 meg RAM. AVG and Zone Alarm disabled whilst trying to resolve this problem.

     

    Project runs OK on Windows laptop and sort of OK on Vista laptop (but that's another problem).

     

    John

×