* Autotext in Baptism

AS allows faster and more convenient creation of source records for Family Historian.
Post Reply
avatar
kenfig
Gold
Posts: 19
Joined: 17 Sep 2011 13:14
Family Historian: V7

Autotext in Baptism

Post by kenfig » 22 Mar 2023 12:00

Hi Nick

Just come across a small problem when editing a table for baptisms. When attempting to modify the table, delete column no longer works, only a cell is deleted. This has only happened since version 7.7.2.

Best wishes

Mike
Mike Sheppard

User avatar
ChrisRead
Famous
Posts: 146
Joined: 10 Mar 2007 17:02
Family Historian: V7
Location: Wells, Somerset, England

Re: Autotext in Baptism

Post by ChrisRead » 22 Mar 2023 12:19

Ah, that explains something I was seeing but didn't really think about it at the time. Wasn't baptism, but can't be sure.
Chris Read
Family Historian and Ancestral Sources user.

Researching the READ family and the myriad other relations that turned up.

User avatar
NickWalker
Megastar
Posts: 2401
Joined: 02 Jan 2004 17:39
Family Historian: V7
Location: Lancashire, UK
Contact:

Re: Autotext in Baptism

Post by NickWalker » 22 Mar 2023 20:59

kenfig wrote:
22 Mar 2023 12:00
Just come across a small problem when editing a table for baptisms. When attempting to modify the table, delete column no longer works, only a cell is deleted. This has only happened since version 7.7.2.
Thanks for letting me know Mike. The fix for rich-text tables in v7.7.2 had a side-effect of creating every table row as a separate table. So deleting a column was correctly just deleting one cell as currently all tables only have a maximum of one row. This will be fixed in the next update.

Nick
Nick Walker
Ancestral Sources Developer

https://fhug.org.uk/kb/kb-article/ancestral-sources/

User avatar
ChrisRead
Famous
Posts: 146
Joined: 10 Mar 2007 17:02
Family Historian: V7
Location: Wells, Somerset, England

Re: Autotext in Baptism

Post by ChrisRead » 22 Mar 2023 21:45

The fix for rich-text tables in v7.7.2 had a side-effect of creating every table row as a separate table. So deleting a column was correctly just deleting one cell as currently all tables only have a maximum of one row. This will be fixed in the next update.
Funny, as when I saw the behaviour, I thought, huh!, that's just like each row is a table. I was familiar with the effect from doing my cunning multi-table auto-text templates (that broke :D ).
Chris Read
Family Historian and Ancestral Sources user.

Researching the READ family and the myriad other relations that turned up.

Post Reply