Family Historian User Group

I agree that is a reasonable interpretation. All the plugin does is prepare the batch file with appropriately formatted commands, then hands over the copying process directly to Windows. This is what makes it run so quickly, as there is no FH processing overhead. This type of access problem should b...

I suggest that a more general discussion of coding for emulator compatibility is best held over until we have the first draft of the KB page, which I’ve deliberately held fire on pending resolution of this specific issue. However, I think we’re there now so I’ll post something next week. I think I’l...

I had to make one minor change to fully support the current "out-of-the-box" repository version of WINE, but that is specific to Linux, not Mac. Don't make additional changes to the library just to support Linux - it will be a small community of tech-savvy users, and they probably wouldn't...

Sorted. With parameters passed individually, it quickly became clear that the only two that were being accepted were Name and Path. That's clearly not right, as we know WINE fully supports file timestamps, so the problem must be in the function that populates your table of attributes. TBH, I found y...

Interesting - I remember commenting back in 2022 when the Windows backup plugin was developed that the original version didn't run under WINE, so it could be a long-standing issue that has not been diagnosed.

It's definitely at the line that gets file attributes, see screen grab below: Screenshot from 2024-06-28 12-34-54.png Also if I change line 313 to simply local tblAttr = {} and change line 358 to local strPath = tblAttr.path or '' to allow for tblAttr.path not being defined, the plugin runs to compl...

Still no joy. We know that fhFileUtils() works fine (once the unsupported attributes are removed). The most obvious difference is that fhFileUtils() uses luacom.pairs rather than the enumerator method, but it's not that on its own, as I know that the enumerator approach works ok in isolation. Before...

Unfortunately, it's still failing, with a similar error at the same place. I wonder if the root cause is somewhere in the luacom routine? Trying to debug the plugin is a non-starter, due to its complexity, but if you have a very short model script that uses the same underlying approach to generate a...

As a general comment, I think that’s the right approach. I use custom attributes and flags to record and highlight matches and MRCA, and that’s exactly the same in versions 6 and 7.

Like the previous poster, I don’t find the FH7 built-in DNA tools that useful, so don’t upgrade just for that.

No - just no bugs that are deemed sufficiently urgent to distract CP from whatever they are focused on at the moment, be it FH 7.1 or 8.0. At least one of their major competitors appears to have moved to an annual cycle of major updates. While it keeps the product "fresh" and "modern&...

After 3 1/2 years they should surely have ironed out the problems that would have appeared after release. I think you'll find that the current release is rather more than bug fixes - it's a far more capable and refined product than it was in December 2020. Remember that in the real world of having ...

I think it keeps the ID of the “master” record, but the simplest option is to try it out for yourself so you can see the effect on your data.

Take a copy of your project and experiment on that so you don’t have to worry about undoing changes or restoring from backup if you don’t like the results.

To clarify, this plugin imports a RootsMagic ToDo list from a GEDCOM file, which the old FH GEDCOM import discarded. It has nothing to do with the FH6 Research Planner.

It feels like a worthwhile option to be able to selectively export/import defined records and their dependencies such as media to file, as there would be a number of standard sources of interest to lumpers that would be common between projects. If anybody feels sufficiently motivated about it, they ...

Two options then - a simple but fairly limited way or a very complicated but more comprehensive way... :) Which you choose will probably depend on factors such as whether you have a handful of records to copy or dozens, how complex the sources are (e.g. with or without media), or whether the target ...

Only indirectly, by having two instances of FH open side by side, each with one of the projects loaded. Create a new source in the target project and copy the fields across one by one. There is no "Copy/Paste Record" routine, or option to selectively export or import specific records from ...

I always record both sources, as they are independent sources that have arrived at your PC by different routes, even though both originals were completed at the same time. For direct ancestors, I want images of both the GRO Marriage Certificate and Parish Register. If they say exactly the same thing...

To build on Jane’s comment for those interested in the plumbing - Flags are custom fields within the Individual record, so can be both read and set by plugins, or read by queries. Custom lists are not (currently) FH records, and are stored in the GEDCOM header section, which is not generally accessi...

This simple script illustrates the FSO issue. In Windows, it pops up a message box with the short path description of the active GEDCOM file, as expected. Run it in WINE, and WINE (and therefore FH) crashes completely. require('luacom') FSO = luacom.CreateObject("Scripting.FileSystemObject"...

That’s great, Mervyn. Thanks very much, there’s plenty of detail there to feed into the KB draft. I agree with you on licensing, as I have the same issue. CP recognise the absurdity of expecting users to purchase additional licences simply for compatibility and robustness testing of their product in...

This is spun off from Testing plugin compatibility with Mac/Linux , posted as a new thread as it is about an issue with an existing plugin, not general compatibility issues. The legacy backup and restore plugin loads normally in FH7 under Linux Mint/WINE, but when starting the actual backup, stops w...

Thanks Mike. I tested your method, and it doesn't appear to work, as WINE maintains exactly the same folder paths as Windows. Screenshot from 2024-06-09 09-34-14.png I assumed you were using this to get the system disk (usually but not always C:\), then testing for the presence of a C:\users\public ...

Thanks Mike - you are testing for something that should be on a native Windows system only, and I'm testing for something that should be in WINE! I agree that neither is probably 100% bullet proof, but they are good enough for our purposes. There doesn't appear to be an official supported method wit...

It's easy for people with (presumably) no training in mathematics or statistics to bandy around these large numbers without any real understanding of their magnitude, but to put it into context, even a 12 character random password based on 50 different characters (numbers, letters, punctuation) has ...

As far as I know, there are no Mac/Linux users who contribute plugins, and I think I am the only current author who tests in Linux before publishing. For most plugins, compatibility is not a problem. The UI may look a little odd, but it still runs. However, I have come across several scenarios in my...