Family Historian User Group

Interesting to see those differences - I have bought several small SSDs to either revive an older Windows or Linux system or in a USB3 caddy for Raspberry Pi, and the going rate for a mainstream brand (Crucial, Kingston, etc) is £25 for 250 GB and about £40 for 500 GB. It’s not the latest or fastest...

Playing devil's advocate, there is no reason why projects can't be on the small local drive and media elsewhere. Remember that the built-in FH Backup is really just a backstop for those that don't have robust general backup protocols. For many users, backing up FH project and media data is just anot...

Yes, it is not advisable to have various Projects in different locations. Why not? I have a live FH Projects folder for actual research projects, and a second FH Projects (Development) folder for test projects. It works very well, and I can easily flip between live and test projects using the Recen...

Has anything else changed on your system recently, such as a new video card or display resolution? If not, it might be one of those odd instabilities that's only fixed by fully backing up your data and settings and reinstalling FH, but let's see if anybody else chips in with further diagnostic sugge...

I won't reopen the "why do you want to do this?" question, as that was discussed at some length only a few days ago. The answer to your current "how" question is actually quite straightforward: Create a new folder off the root using a short name, such as \FH Open your current pro...

Tamara’s e-mail contact is still enabled, but I think that was the intention, and relying on spam filter to get rid of the rubbish.

My experience is that routine e-mail notifications (which I enable for threads related to my plugins) usually get through, but occasionally end up in Junk Mail.

Can’t remember the exact syntax as I’m away from the computer, but dialog:map() places all the elements in the form without actually drawing it. Does that help?

I’d forgotten that one. It doesn’t impact me as I don’t use AS, but that problem of mangling text-based dates on transfer has been around forever. I generally avoid numerical dates for anything other than trivial applications, as I spent most of my former professional life in global teams that had t...

Does FH take any notice of the Windows locale setting and date format? It seems to be the app date format options that drive how entered and reported dates are presented.

My FH and Windows short date formats are different (yyyy-m-d and dd-mm-yyyy, respectively), with no issues that I’ve noticed.

Agree - you only need to read the Registry if you want to remind users what their setting is. None of the main app forms do that (not even the Date Entry Assistant), so it would be the plugin leading the way if you included it .

I think we are well down the burrow now, but this is what I meant: Capture.png I have a second user account that I created a while ago when exploring how the options worked. I have disabled e-mail contact for the test account, so that option does not appear in my normal account. Private messages are...

I suspect Helen will chip in shortly to clarify, but the key point seems to be that sending direct messages is already deactivated for all users, but receiving direct messages is under user control. :? I’m only just twigging that there are two distinct mechanisms - I don’t use many other forums so d...

Oh dear - what a bu**er's muddle...

John - I've been experimenting as well, and how FH interprets numeric date formats seems to be determined by the preferred Short Date Format in the Preferences menu. I copied your function, and was puzzled that it was returning false for today entered as either '13/3/2024' or '13.3.2024'. However, m...

I read it as meaning direct E-mail throughout, as in “send E-mail to AdrianBruce” for example. The recipient receives an E-mail from FHUG forwarding the initiator’s message and reply E-mail address. If the intended recipient has messages disabled, that option is not visible, so they cannot receive a...

I’m not clear why a user would want or need to do that. I read John’s PS as simply being that the plugin is aware of the user’s date preference, so it understands how to interpret a numerical date format. That comes from reading the relevant Registry key, but why should the plugin need to change it?...

tatewise wrote: ↑13 Apr 2024 17:56 Otherwise, I think it involves dabbling with the Windows Registry!

Which must be read-only for published plugins of course, not changing a system setting, even temporarily…

As a general UI design point, I think scroll bars are better for a large form where it will all need completing, and tabs are better if there is a hierarchy of options (so common options are in the default tab, with others in minor tabs). If you go for tabs, you will still have to ensure the UI cope...

Ah - if the Birth Certificate is not always the first source, it does get more complicated. However, your approach is the way to go, looping though the sources and testing each in turn with a combination of pSource:MoveTo(pI, Data Reference) and pSource:MoveNext('SAME_TAG') . Examples in the plugin ...

Asking people to behave shouldn't be controversial, but it got off to a bad start with a false statement in the very first sentence of the thread. I've read the ensuing comments, and had some further one-to-one discussion with Helen offline. If PMs are off, users who are happy to receive such messag...

Yes, John's version is easier as it gets the source title directly without having to worry about converting links. For this exercise, that's all you need. Any of the following should work: pTitle = fhGetItemPtr(pI, '~.BIRT.SOUR>TITL') pTitle = fhGetItemPtr(pI, '~.BIRT[1].SOUR[1]>TITL') pTitle = fhGe...

For a quick and dirty just for single use, I would be tempted to do it the other way around, but it does involve links between records, which can be more difficult to get your head around. Loop though Individuals, not sources. Get the pointer linking to the birth fact source ( fhGetItemPtr(pi, '~.BI...

{3state = 'YES'} is an alternative and shorter version of {['3state'] = 'YES'}. IUP controls are defined as Lua tables, and the short version is permitted only if the key is a valid Lua variable name. If you use the full version, it should work as intended.

It was a useful prompt that I had omitted to update the help file with a description of the more detailed criteria for excluding family records from export. Now fixed.

Thinking about this scenario in more detail, I think there is an unavoidable difference between how lumpers (which FTM forces you to be) and splitters record this type of note. Lumpers have to put it in the citation, as there is nowhere else for it to go. Splitters create a separate source for each ...