#Change where anysend downloads files movie#
#Change where anysend downloads files upgrade#
#Change where anysend downloads files code#
#Change where anysend downloads files download#

Or if the main FieldWorks Language Explorer window appears, choose File -> Project Management -> Restore a Project.

If the welcoming Language Explorer dialog appears, click “Restore a project from a backup file”.

Open the Restore a Project dialog by doing one of the following:.

fwbackup in order for the FieldWorks restore function to work. zip, you will need to rename them first to. If you find that your browser (e.g., I.E.) has renamed the files to.

#Change where anysend downloads files download#

Download and save this file to your computer.

Click one of the sample projects, such as “Sena 3”.

Lela-Teli 3 – 2 MB (Data Notebook data).

Lela-Teli 2 – 2 MB (Data Notebook for training).

Sena 3 – 15 MB (Lexicon and Texts data).

Sena 2 – 14 MB (Lexicon and Texts for training).

For versions 8.0.5 – 8.3.0, use this sample data:.

The version of sample data you need will depend on the model of the version of FieldWorks you are using.

Sample projects are no longer being included in the download packages.

#Change where anysend downloads files upgrade#

To use FLExTools with this version of FieldWorks, you will need to upgrade to version 1.1.4.To use Phonology Assistant with this version of FieldWorks, you need to upgrade Phonology Assistant to version 3.4.6 or later.Type-ahead doesn’t work on custom fields referring to custom lists.

#Change where anysend downloads files code#

Unicode Character Editor fails to process code points out of plane 0.

Right-click menu is inappropriate for Status and Confidence fields.

Interlinear SFM import fails with Unicode to Unicode converter.

Semantic Domain’s Suggest feature is too prolific when there is more than one word in the Gloss field.

Workaround: Use Open and then select Sena 3.

The Sena 3 (sample project) link doesn’t work on the new Welcome dialog box the first time the dialog opens.

This will be addressed in a development effort to redo Dictionary Configuration.

In Dictionary Configuration, the check box under sense that says “display each sense in its own paragraph” is not working properly.

in 2012), FLEx will crash when you try to open the project.

If you created a custom field in WeSay and used a previous version of LIFTBridge with FLEx (e.g.

Which entries belong in which inflection template slots and some other morphological grammar facts stored on a lexical entry. Some FLEx data is not handled well yet by this collaboration method.

Send/Receive Lexicon depends on the LIFT standard.

Send/Receive Lexicon should not be used to pass data between two or more FLEx users.

When both users change the properties of the same style, the resulting merge conflict message does not state the conflicting style settings.

If a user subsequently removes the link to the file due to the current restrictions, the warning messages continue to be displayed at each send/receive operation if the file is still in the project folder.

#Change where anysend downloads files movie#

No movie files of any size are being transferred. Linked media files over 1MB in size are not being transferred.you closed the Messages window then need to reopen them) wait for 5 seconds and try again.

Using any Send/Receive commands in quick succession usually causes a message to pop up which claims that FLExBridge is already running.If you add a question or add a message to a merger conflict/notification, it is not possible to edit or delete those comments subsequently.A phoneme may have incompatible phonological features and an entry may have incompatible inflection features. If both users edit the same phonemes, or add inflection features to the same lexical entry, the results may need subsequent editing.The Text Chart is changed incorrectly (words are moved to emptied cells) after another user deletes some charted words from the text.The menu item “Copy (Ctrl+C)” isn’t working on the “Conflict Detail” dialog box.You cannot have non-ASCII characters in the FLEx project name to use Send/Receive.The subsequent send/receive would send a huge number of changes to all the other team members, effectively restoring the old version of the project on every team member’s computer. It is strongly not recommended to restore over (replacing) an existing project with which you are collaborating using send/receive.If you want to track our progress on these and other issues, follow one of the links below and sign up for an account on our JIRA system. Uncheck the box labelled “Share projects stored on this computer.” You can do this in File > Project Management > Project Locations and Sharing. If you have used older-style sharing over a local area network (projects have the extension fwdb), you need to turn off that way of sharing (revert to fwdata format) in order to try Send/Receive for collaborating.