Re: [LegacyUG] Hashtag assignment - generates a temporary Unknown spouse

[Cathy Pinner]

The problem with new people not immediately being on Index View is to do 
with having Include Married Names or Include Alternate Names on but not 
both on or both off. I thought this was fixed but apparently not. There 
are other bugs with Index View and Name List if you have one on and not 
both on or off.


I don't follow your first problem. What do you mean by "select the tree, 
view in Descendant View"
You mean you highlight a tree and then click Select so you are taken to 
the named person in the tree in whatever view you were in when you went 
to View - Trees. And you go to Descendant View or were on Descendant 
View. "scroll up?"  Do you mean you use the Go to Father or Go to Mother 
to navigate up the tree on Descendant View?

Then what?

Cathy


Ian Thomas 
Tuesday, 5 February 2019 3:52 PM

I have just begun using hashtags, and it should be useful. Currently, 
I am going to the Treelist,  refreshing the list,  and using the “Add 
a hashtag to the entire tree” – bottom option (button).


That seems to be a rapid and easily-understood way to assign hashtags 
accurately and quickly, and to keep the number to a minimum initially 
(until I know what works best for me).


When I do this, then select the tree, view in Descendant view, and 
perhaps scroll up to earlier ancestors in that tree (the earliest are 
seldom the “main identity” of the trees that have been determined), in 
some cases I see  a spouse (Unknown), who may have a birth and/or 
death date – which seems to reflect those of a supposed spouse- in the 
row above.


This sounds complicated but is quite a simple operation. I suspect it 
is a harmless bug.


If I select the Unknown, my display reverts to my starting couple 
(forget the proper term), and the Unknown isn’t seen again. If I 
select another individual (row), that individual is displayed and the 
Unknown artefact disappears.


I suspect it is something to do with indexing.

Another bug that has persisted for months, is that I find that one or 
more recently-added individuals cannot be located in the Index view 
until I enter their given names (or their surnames – it varies); after 
a few tries, I can find the individual.


Again, I think it is an related to indexing – not a problem, since it 
self-corrects after a time. I don’t bother with any sort of File 
Maintenance until I’m ready to close Legacy Family Tree (9, Deluxe, 
latest update always) and do the usual backup.


Perhaps these are both related to disk caching – I do find that 
(outside of Legacy), File Explorer operations on my multi-disk system 
often require an F5 refresh.


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/

[LegacyUG] Hashtag assignment - generates a temporary Unknown spouse

[Ian Thomas]

I have just begun using hashtags, and it should be useful. Currently, I am 
going to the Treelist,  refreshing the list,  and using the "Add a hashtag to 
the entire tree" - bottom option (button).
That seems to be a rapid and easily-understood way to assign hashtags 
accurately and quickly, and to keep the number to a minimum initially (until I 
know what works best for me).

When I do this, then select the tree, view in Descendant view, and perhaps 
scroll up to earlier ancestors in that tree (the earliest are seldom the "main 
identity" of the trees that have been determined), in some cases I see  a 
spouse (Unknown),  who may have a birth and/or death date - which seems to 
reflect those of a supposed spouse- in the row above.

This sounds complicated but is quite a simple operation. I suspect it is a 
harmless bug.

If I select the Unknown, my display reverts to my starting couple (forget the 
proper term), and the Unknown isn't seen again. If I select another individual 
(row), that individual is displayed and the Unknown artefact disappears.

I suspect it is something to do with indexing.

Another bug that has persisted for months, is that I find that one or more 
recently-added individuals cannot be located in the Index view until I enter 
their given names (or their surnames - it varies); after a few tries, I can 
find the individual.
Again, I think it is an related to indexing - not a problem, since it 
self-corrects after a time. I don't bother with any sort of File Maintenance 
until I'm ready to close Legacy Family Tree (9, Deluxe, latest update always) 
and do the usual backup.

Perhaps these are both related to disk caching - I do find that (outside of 
Legacy), File Explorer operations on my multi-disk system often require an F5 
refresh.

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/