There seems to be a second update today. I just installed update 6.0.0.69
of 11 Oct 2005 and this problem persists for me.
For comparison's sake, choose any event where you use [~place] in the event
sentence. Then click "Edit" and look at your sentence which is listed below
the "Refresh Sentence" button. For example, my event sentence definition
reads, "[HeShe] moved to [~Place] [onDate].[Sources] [Notes]." On the
screen it reads, "He moved to , Miller County, Georgia, USA in 1857." The
short form of the location using my data should eliminate the leading
(floating) comma and the mention of USA, both of which are pulling from my
long location name.
Does this make sense? Maybe Dave meant that it would be in the next update
after the ones today. On the other hand, if I have missed something, please
let me know.
Thanks,
Gail Rich Nestor
From: "Robert Carneal" <[EMAIL PROTECTED]>
It is still broken for you? Then perhaps we are not looking at the same
place you are. It is working for me, which means we are not on the same page
somewhere.
Gene Falls wrote:
I just installed update 6.0.0.68 and it is still broken
Gail Nestor wrote:
Yay!! Thanks so much!
From: "Dave Berdan" <[EMAIL PROTECTED]> This has been fixed and
will be in the next update...
From: "Dennis Kowallek" <[EMAIL PROTECTED]> It appears that ~inPlace is
still broken (this bug goes back to V5).
Instead
of displaying the short location name on the bottom of the Edit Event
window, it still displays the long location name.
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
