Menus

A list of all Flying Logic menu commands and their functionality

Application Menu (Mac)

About Flying Logic	Displays version information and credits.
Preferences...	Displays the Preferences dialog. See Preferences.
Quit Flying Logic	Quits Flying Logic. The user is prompted to save changes to any unsaved documents before quitting.

File Menu

New Document	Creates a new, blank document.
New Document From Selection	Creates a new document containing copies of any elements that were selected in the current document.
Open...	Opens an existing document. New documents can also be opened by dragging a Flying Logic document to the application icon (Windows: in Windows Explorer, Mac: in the Finder or Dock, Linux: see your window manager documentation.) Template files can also be opened, which open as new Untitled documents containing the contents of the template. Existing exported domain files can also be opened, which causes a new, blank document to be created with the domain automatically imported.
Open Examples...	Allows browsing and opening of a variety of provided example documents. Example documents open as new, untitled documents so you can modify them and save them elsewhere.
Open Recent	Select a name from the submenu to re-open a recently open document.
Close Tab	Closes the current document tab. The user is prompted to save any unsaved changes. If only one document is open in a window, this closes the document and window.
Close Window	Closes the current document window. If multiple documents are open in a window, the application attempts to close them all. The user is prompted to save any unsaved changes.
Save	Saves the current document. If the document has not been saved before, the user is prompted for a file name and folder to save to.
Save As...	Saves the current document in a new location and/or with a new name.
Save as Template...	Saves a copy of the current document in a new location with a new name, and changes its filename suffix to .xlogic-t. When a template file is opened, it opens as a new, Untitled document, but starts with all the content that was saved with the template.

Import Submenu

Import Diagram from CSV...	Imports a diagram from a simple CSV (comma-separated values) text document. For the format of this document, see the Flying Logic Scripting Guide.
Import from MS Project...	Imports a diagram from an MS Project document in MPP, XML or MPX format. The diagram may include extra elements to properly represent features from MS Project. See the section Notes on MS Project Import and Export in Project Management.

Import via Script Submenu

Open Script...	Executes the selected script as an importer of the current document. For convenience, the submenu also remembers the last four scripts run this way.

Export Submenu

Export of diagrams to PDF, PNG and JPEG support a “Save Ink” option identical to that available when printing: group backgrounds are not shaded.

When to use PDF?

PDF is the most desirable format for publishing and all other applications that do not require a “bitmapped” graphics format (such as JPEG or PNG), as PDF images will scale to any size with no loss of quality. PDF also supports transparency, and will look good when overlaid against backgrounds containing images or textures.

When to use JPEG?

JPEG images are compressed, and may show a slight fuzziness around the edges of lines and text. Also, JPEG images do not support transparency, so programs that overlay images on backgrounds (such as presentation software) will show the JPEG as completely obscuring any background. Exporting the image to PDF or PNG is recommended when transparency is desired.

When to use PNG?

PNG images use a “lossless” form of compression that does not result in the edge-fuzziness associated with JPEG images. Also, PNG images support transparency, and will look good when overlaid against backgrounds containing images or textures.

Note numbers are fluid

Note numbers change as annotations are added and removed from the document, and should not be relied on to stay the same across document revisions.

Export to MPX is deprecated

Export to MPX is only still provided for users who must use older versions of Microsoft Project that do not import the XML format above. Certain attributes may not be exported correctly when using this command.

Exporting to MS Project

When exporting to MS Project, the following conversion rules apply:

• All entities are converted to MS Project Tasks of the same effort assigned in the Entity tab of the Element inspector when Project Management is turned on, or 1-day effort if no other effort has been specified. Zero-effort tasks are converted to MS Project milestones. The name of the task is the entity’s title. The Text1 field of the task is set to Entity. The Text2 field of the task is set to the entity class name. The Number1 field of the task is set to the confidence value of the entity.

• All junctors are converted to MS Project milestones. The name of the task is the name of the junctor operator. The Text1 field of the milestone is set to Junctor. The Number1 field of the task is set to the confidence value of the junctor.

• All groups are converted to MS Project summary tasks. The name of the summary task is the title of the group. The Text1 field of the summary task is set to Group.

• All edges are converted to finish-to-start dependencies with no lag.

• Notes for entities, groups, and junctors become notes on the corresponding tasks. Notes on edges are not preserved, because MS Project does not support notes on task dependencies.

Export via Script Submenu

Edit Menu

Run Script Submenu

Entity Menu

Redaction Modifies the Document

Redaction doesn't simply hide the redacted data in the document, it actually replaces it. Make sure to save an un-redacted version of the document for your own use.

Group Menu

View Menu

Domain Menu

Format Menu

Window Menu

Help Menu