search

cdfarrow / flextools

Python scripting utility for SIL FieldWorks Language Explorer (FLEx)
Other
16 stars 5 forks source link

Fix to not have to close FLEx #17

Closed rmlockwood closed 2 years ago

rmlockwood commented 2 years ago

I've found that if I delete the lock file in the FLEx database project folder, it works fine to have FLEx open and run FLExTools modules that don't modify the database. It would be great if this could be part of FLExTools functionality that when it does an OpenProject operation that is not in modify mode, it automatically deletes the lock file.

cdfarrow commented 2 years ago

Thanks for the suggestion, but I'm not sure if it is a good idea to mess with Flex's lock mechanism. I'll ask Ken for his input on this.

bbryson commented 2 years ago

There is a workaround. In FLEx, do File/Project Management/FieldWorks Project Properties. Click the Sharing tab. Tick the box for "Share project contents with programs on this computer."

cdfarrow commented 2 years ago

More explanation from Jason Naylor: Projects that have Scripture books in them open in [shared] mode automatically so that Paratext integration is possible without telling people to go find the option, but other projects will need it set.

cdfarrow commented 2 years ago

This doesn't require a fix in FlexTools, but I've updated the error message and documentation, so those changes will be in the next version (2.1.2).