C# Класс SIL.FieldWorks.FieldWorks

Dummy method to be used for InvokeOnEventsThread which is used as a way to initialize the Broadcast window and prevent errors on shutdown.

Opens the specified (newly-created) project. This may start a new FieldWorks.exe process to handle the project if no FieldWorks processes are running for the specified project.

Get a list of all projects (by ProjectName) currently open by processes on the local machine.

Starts the specified FieldWorks application.

Archive selected project files using RAMP

Backup the project.

Backs up the project that is about to be restored.

Close any main windows. This is needed to implement changing the projects folder location when multiple projects are running. (See FWR-2287.)

Closes all main windows for the specified application ignoring any errors that occur.

Closes the splash screen

Commits the and disposes the FdoCache. This is usually called on a separate thread.

Copies all files and folders in the specified old directory to the specified new directory

Creates a new main window and initializes it. The specified App is responsible for creating the proper main window type.

Lets the user create a new project

Creates a remoting server to listen for events from other instances.

Remote request calls can hang if the service is no longer active but the port is still in the listening state. This method calls the IsAlive method on the requestor to verify that it is valid.

Lets the user delete any FW databases that are not currently open

Displays the error.

Shows the error message of the exception to the user.

Does the restore.

Ensure a valid folder for LangProject.LinkedFilesRootDir. When moving projects between systems, the stored value may become hopelessly invalid. See FWNX-1005 for an example of the havoc than can ensue.

This method gets called when we open the FDO cache.

Create the specified Linked Files directory only if it's the default Linked Files directory. See FWNX-1092, LT-14491.

Executes the requested action with ALL FW applications temporarily shut down and then (re)starts the applications in a sensible order. At the end, we're guaranteed to have at least one app started or FieldWorks will be shut down.

Executes the requested action with all FW applications temporarily shut down and then (re)starts the applications in a sensible order. At the end, we're guaranteed to have at least one app started or FieldWorks will be shut down.

Cleanly exits the FieldWorks process

If no applications are running anymore, just shut down the whole process

Displays the Project Location Sharing dialog box

Follows the specified link request for this project.

Handles the Activated event of FieldWorks Main Windows.

Handles the Closing event of FieldWorks Main Windows.

Gets the application for the specified application name or abbreviation.

Get the available localizations.

Gets the command-line abbreviation for the specified application name.

Gets the default application to start for the project specified in the the command-line arguments.

Gets a HelpTopicProvider for the specified application if possible. Falls back to getting the HelpTopicProvider for another application if the requested one is not installed. Will not return null (but it could throw an exception if no FW app is installed).

Gets an existing app or creates a new one for the application type specified on the command line.

Get or create a FLEx application. This method does not ensure that the returned application is fully initialized.

Gets the status of the previous attempt to startup the specified application.

Determines the match status for the project used by this FieldWorks process and the specified project. This method is thread-safe.

Attempts to shut down as nicely as possible. Typically this method doesn't do anything when the application is shut down normally (e.g. the user has closed all of the open main windows) because the applications will have already been disposed of. Thus, any exceptions that are thrown are ignored by this method as there is no guarantee that the application is in a valid state.

Any exeptions that are thrown are logged to the log file.

Attempts to shut down the specified application as nicely as possible ignoring any errors that occur.

Handles a link request. This handles determining the correct application to start up and for the correct project. This method is thread safe.

Handles a request to restore a project. This method is thread safe.

Handles a request to restore a project. This method is thread safe.

Catches and displays a otherwise unhandled exception.

previously AfApp::HandleTopLevelError

Catches and displays otherwise unhandled exception, especially those that happen during startup of the application before we show our main window.

Initializes the specified application and creates a new main window for it. Also does application-specific cache initialization.

Return true if a folder belongs to FieldWorks, that is, it is one that we recognize has having a proper place in the Projects folder.

Determines whether any FW process is in "single user mode".

Starts or activates an application requested from another process. This method is thread safe. See the class comment on FwLinkArgs for details on how all the parts of hyperlinking work.

Launches the application when requested from the command-line.

Launches a restore project when requested from the command-line.

Migrates the user's databases to FieldWorks 7.0+ if they haven't yet migrated successfully (and the user actually wants to migrate).

Moves the external link directory and files to the new FW 7.0 or later location.

Moves all of the projects in the specified old project folder (including any subfolders) to the specified new project folder.

Check whether we must copy the project folders and files because the new Projects folder is on a different device than the old Projects folder.

Opens the specified project. This may start a new FieldWorks.exe process to handle the project if no FieldWorks processes are running for the specified project.

Opens the specified project by starting a new FieldWorks.exe process.

Opens the specified project by starting a new FieldWorks.exe process.

Handles a project name change.

Records the last running application for the current project.

Rename the database.

Returns some active, non-disposed application if possible, otherwise, null. Currently Flex is preferred if both are re-opened.

Resets the state of FieldWorks to allow a forced shutdown. Should only be called when a lethal unhandled exception is thrown.

Restores from the backup specified in restoreSettings, replacing the current version of this project (requires restarting apps and the cache).

Restore a project.

Restore a project.

Runs the specified delegate on any other FieldWorks processes that are found. If no other FieldWorks processes are found, then the delegate is not called.

Sets the exception handler.

Sets the UI culture.

Sets information about the current database to the ErrorReporter so that it can be reported with a crash.

Shows help for command line options.

Displays the splash screen

Shutdowns the specified application. The application will be disposed of immediately. If no other applications are running, then FieldWorks will also be shutdown.

Releases unmanaged and managed resources

Returns true if valid command-line args created this projectId. Returns false with no exception if no -db arg was given. Returns false with exception if invalid args were given.

Tries to find an existing FieldWorks process that is running the specified project. See the class comment on FwLinkArgs for details on how all the parts of hyperlinking work.

Attempts to find another FieldWorks process that can handle the specified link.

Attempts to find another FieldWorks process that can handle a restore for the specified restore project settings.

For some reason, setting an Xkb keyboard for the first time doesn't work well inside FieldWorks. The keyboard is actually set (although it may take effect only after the first one or two keystrokes), but the indicator on the system icon bar does not change. Setting several Xkb keyboards at this point seems to fix the problem for when the first one is set different than the default keyboard. This hack is not guaranteed to work, but it does seem to help in most scenarios. See FWNX-1299.

If you can think of a better solution, by all means replace this ugly hack! It took me a day of work to come up with even this much. I tried setting the multiple keyboards in succession inside Palaso.UI.WindowsForms.Keyboarding.Linux.XkbKeyboardAdaptor.ReinitLocales() but it didn't work doing it there for some reason.

Updates the projects default directory.

Attempts to turn project sharing on or off if not already in the requested mode.

Writes the current executable path to the registry. This is used for external applications to read on developer machines since the RootCodeDir on developer's machines point to distfiles.

Write to the splash screen

Compare the strings first by length (longest first), then normally if the lengths are equal.