Family Historian User Group

Oops, apologies - all I thought I did was overwrite the two shared files, but I seemed to have created a new link somehow. I've deleted the superfluous links, which unfortunately kills the earlier version, but I have successfully edited the link in my recent posting. It is too late for a non-admin t...

The draft plugin and associated help file have now been updated to version 0.3 ( download link ). Main menu.png The most significant change is the addition of support for part-frame images cropped from a larger file (adapted from Adrian Cook’s kindly provided template). A new menu option allows the ...

It might be worth trying to restore the backup from the network drive using the Backup and Restore Family Historian Settings via Windows plugin to see if that shows the same error. The easiest option will be to delete one your store plugins before running the restore, and select the Discard changes…...

My initial diagnosis was correct - changes to Family Records were not be cascaded to the GEDCOM extract file and onwards to RM. Version 2.4.1 is now in the Plugin Store.

It works! Stage 1 was extracting the essential code to duplicate the image produced by IrfanView (above). That works perfectly with the filename and crop hard coded into the script, so stage 2 will be to generalise it to integrate into the plugin script and cope with other supported formats such as....

Excellent, thanks very much Adrian, that looks just what I am looking for!

It's raining on the Velux window above my head, so let's have a play...

Thanks, Helen. I'm trying to work out from the rather opaque documentation exactly how to crop an image so I can follow that code in the Export Gedcom File plugin, but I'm finding the guide much harder to follow than for iuplua (and that's not a terribly high bar!). It's probably easier to work from...

Thanks for the feedback, Tony. I’m not familiar with Mac Family Tree, but its companion iPad app (MobileFamilyTree) looks very good from the slick promo video. It’s only £15, so I’m tempted to buy it anyway for the extra bells and whistles over the perfectly adequate but more limited GedView. I’ll a...

It might be worth reporting to CP. If the TMG direct import has created an empty Fact Set file, it sounds like a possible bug. I've been experimenting with how FH handles empty Fact Sets to see if it has any implications for my own plugins. I created an empty Fact Set file in the Sample Project fact...

Sorry about that John - it suggests that the partial update is not seeing changes in Family Events correctly. There may also be a TreeShare issue in there as well as it translates between the RM way of seeing families and the Ancestry way. I'll investigate further tomorrow.

Perhaps inevitably, a day or two turned into a week, but I have now updated the download link at the top of the thread to point to version 0.2, shown here demonstrating its automatic support for the user's preferred Property Box font, which gives a look and feel very similar to that of FH itself. Ex...

You’ve fallen into the trap of seeing it as the author, not the reader. Mike’s plugin refers to imlau, so that’s the term I search for. How am I supposed to know that the library is called IM without finding it in the KB? It’s turning into a much longer discussion than I anticipated, but it’s an imp...

No - I was looking for ‘imlua’, which is the exact name of the library. The Algolia search found nothing in the KB using that term, and only the old forum thread that didn’t link to the KB (probably because it pre-dated the KB page). I suspect that it is unfixable, but bottom line is that the search...

Curious - searching for 'imlua' (the exact five letter word used in the KB article) finds nothing in the KB and only the 2018 thread plus this one for the forum, but searching for 'IM Lua' does find the reference as the only KB item returned (even though that exact string does not occur on the page)...

Got it thanks. A search using the box at the top of the page doesn’t find it, so important to remember that it doesn’t appear to be a full text search…

The updated draft of the Export Public GEDCOM File is more or less ready for posting, but one quick question on processing media files please. A separate thread as it is not relevant for 99.9% of readers. Media are currently exported as full frame images only. My ideal scenario is to automatically p...

I’ve used ExifTool in the past for bulk writing of exif data to image files, so it should be fairly straightforward to generate a series of commands for the individual updates, assemble them in a batch file, then execute the file from the plugin using fhShellExecute(…) or os.execute(…).

That's my instinct as well. I did have Address in mind as a possible addition, but only as a straight export. However, it's probably not supported by enough apps to make it worthwhile, particularly as the main focus of this plugin is very easy export of the essential data for public sharing rather t...

Further testing reveals one apparent limitation of FMP trees. Using this draft, custom family facts (both events and attributes) are discarded when importing the GEDCOM to FMP. Ancestry keeps these, and assigns them to both partners in the family. The Export Gedcom File plugin appears to have the sa...

I’m not enthusiastic about supporting a format such as GEDCOM 5.5 that has been obsolete for years, but it will take 10 minutes to add a basic 5.5.1 option to my working copy, so I’ll probably test that in at least RM and Legacy current versions to see if it works.

PS - the final version will have a help page that describes the options in more detail, but that is disabled in the draft as the Plugin Store does not properly support help pages for unpublished plugins.

Correct Adrian - ticking the box just changes the description from Census to Residence. All the relevant details are exported in both cases (provided that events are not limited to BMD of course). Ancestry is a little odd in how it behaves here. It does support and display Census events, but some fe...

It could be included if there is demand for that facility, but I think it would be limited to a simple yes/no tickbox and only supporting core GEDCOM 5.5.1 OBJE record features (so no FH enhancements such as face/detail clips), with file paths converted to their full location, not relative to Projec...

Mike, thanks for the speedy response (I didn't think you would be long ;)), but I think you have missed the point of what I am aiming to do. I am not supporting any specific target products. I am providing an export of core essential data that generally transfers well by GEDCOM. I do not need to tes...

This new draft plugin was prompted by recent activity around Mac/Linux compatibility and the discovery that FH cannot connect to an external database via plugin when running under WINE/Crossover. It also revives a concept that I floated some time ago but did not pursue - a generic GEDCOM exporter th...