Family Historian User Group

Hi Nick, This idea has come about due to our recent work on templates combined with my own 3+ week effort adding & converting external Word transcriptions to Rich Text in Text from Source. I know it wasn't essential to do, but it does mean things can be made 'neater' and more readable than some of t...

Hi Nick, Has any consideration ever been given to supporting input of Marriage Banns? I have a few in my sources, but they have been created the long way in FH and I thought it would complete the AS set of BMD type sources that are currently available, and uses a sub-set of the information the exiti...

Ok, 7.1.5 seems to have fixed the problem of jumping focus on the main input screen. I'm sure you didn't wake up today expecting three releases in a day. :shock: I'll carry on playing around while I work out the best way to use the maths to try and make the tables work even when changing the column ...

Force of habit to figure out way to reliably reproduce problems. I'll leave it your hands as you have a handle on it. I wasn't sure it it was a single problem or several related ones. I guessed that TITLE had font & fs somewhere inside, and were the common factor.

Tried something else.
I changed the {RTF-HEAD} font in the settings to something other than Default. Doing so makes the problem occur until put back to Default.

I did wonder about the <font> and <fs>, but in principal should be valid. I removed all the font and other extra format related stuff on that first row, but I still got the problem. I removed the whole first table and the problem stopped. I put back it back with just the top row and the problem was ...

Hmm, more intriguing. It seems the focus problem on the normal app is only occurring where a template includes a table (maybe) such as mine. I tried another (1837-) and initially I thought it did it too, but when I went back round the loop it didn't happen, so I'm confused. Here's my template. <tabl...

Using 7.1.4.

Yes, focus problem is fixed in the template editor, but is now occurring on the normal user screen, see the very long thread.

Ok.... The functions appear to work as expected, you are a star. I just need to work out what to do with them :) The WORDNUM is nice, more than I expected, and likely of use to other brave souls doing their own custom templates. I'd only originally thought about individual numbers rather than as a d...

The language thing only stemmed from your comment about ORD being English, so I wondered if you had some plans or it was simply an "in an ideal world" thing. It seems the latter. :) Yes, I forgot that the template in that thread was slightly older than what I had as I have changed the { to [ because...

Scratch that, I think I miss-understood, I need the 7.1.3+ version I assume as it's still doing it, although I swear it worked initially, hence my previous post.

Yup, that seems fixed, thanks so much.

I think you'll find it is under Type: Register rather than Type: Census.

Ok, this is a 3AM idea, but may be a way to minimise my guilt over the .ORD being English :) The idea was to basically make the suffix configurable a bit like how you allow the column widths to be configured by a user. So, they'd be able to set a suffix for each terminal digit (0..9). I had a look a...

Hi, I started getting a very annoying problem when using the auto-text editor. I'm not sure exactly what triggers it as yet, but this is a heads-up and initial report. When working on that template that I posted on the '{' problem thread, at some point it started behaving oddly. At first I thought I...

You are right, and I'm being rather anglo-centric which is remiss of me. From experience I should know better. For the ORD one it maybe possible to take OS language settings in to account, at least for those that are known/understood if was a major issue for people. Or an AS setting to be a little m...

So, this is the 'complete' auto-text sample based on the one I posted before. I have had to keep the fixed column sizes for now until if and when your idea for maths functions happens. I've otherwise tried to stick to the style of existing templates. It has flagged up a couple of functions/keywords ...

So, starters for ten... =MUL[x%y] multiply x by y return result =DIV[numerator%denominator] divide numerator by denominator return result =ADD[x%y] add y to x return result =SUB[x%y] subtract y from x return result Logically leads on to comparisons as we already have =EQUALS[x%y] and =EQUALSNOT[x%y]...

I hesitated to suggest such things, but you're right. Probably need to try some stuff out and come up with some sensible requirements. Oh dear it'll be use cases and requirements analysis next.

That 'secret' trick from Jane makes it a lot easier to create a template fairly quickly. I've come to the conclusion that this approach is nigh on impossible to do if you try and stick to the {RTF-WIDTHx} as they are not in multiples of each other. For what I was wanting, it's not really an issue to...

Ah, my fault, I was in a hurry (she who shall be obeyed) and when I quickly picked something to try, it didn't actually have anything interesting RT wise. Just had another go having seen your post, and yes I see the expected stuff. All makes sense now.

Thanks Jane, this was more about creating a template using the RT editor and then getting it out as Auto-text to use in AS, rather than just exporting a Note box content. Edit: The ctrl-alt double-click brings up the RT editor whereas double-clicking brings up the plain text editor with the option t...

Ah! a man of culture I see.

'always know where one's towel is'

I literally just found the Save as Autotext under the cog menu on the editor, and came back here to say, problem solved. It seems that there is a keyboard shortcut for that too, from what Jane says. :lol: although I'm not sure where or how Jane's suggestion works, as I can't make it happen. We all l...

I realised that it would be nice to give back to the community once this is done. Is there a 'proper' way to export the Rich Text as the FH tag format, as I just went and looked in the GEDCOM to find it, and it seemed to be in that form, albeit prefixed with GEDCOM keywords. Not beyond the wit of ma...