Bummer. It would be useful if a better implementation was also substituted - consistent with the way that both Bing Maps and Google Maps return the LatLong to the user on their maps (which are different, as you would know). In my opinion, the current method in Legacy for manually inputting a location is a nonsense. And if the nlocation name inpout returns a not-found, I always end up somewhere off the coast of the USA. I saw a post from someone on this list, in the last week or so, who had 3 browser windows open to effectively do accurate and reproducible locations to plug into Legacy FT.
Ian Thomas Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Cathy Pinner Sent: Wednesday, 30 August 2017 5:44 PM To: Legacy User Group <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Master Location List maps No, it's still being worked on. It probably won't be in the next update as there's a new beta to test some FamilySearch stuff and that is likely to go to public release before the mapping is sorted. Cathy Ian Thomas wrote: Any word on when this will be fixed? I see that .189 is still the latest version/build of Legacy. Ian Thomas Albert Park, Victoria 3206 Australia
-- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
