Global Toolbars

Opens the Analyzer Summary window pane, which is the primary window pane in the interface. This window pane displays a list of current issues in the project being analyzed. See Analyzer Summary Window Pane and  Viewing Current Issues.

Saves changes to the active file.

Opens a submenu, which lets you open the active file in another application, attach it to an email, or open the Windows folder where it is stored.

Opens a submenu, which lets you select various source control options for the selected file(s):

• Project Opens a submenu, which lets you select a source control action to be applied to the entire project (as opposed to just the selected folder or files):

  • Check In All Opens the Check In dialog, which lets you check in all files in the project into source control.

    When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control.

    You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

  • Commit All Opens the Commit dialog, which lets you commit all files in the project into source control.

    If your project is bound to Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote. If your project is bound to Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine.

    You will see this option if your project is bound to Git or Subversion.

  • Submit All Opens the Submit dialog, which lets you submit all files in the project into source control.

    When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control.

    You will see this option if your project is bound to Perforce.

  • Check Out All Opens the Check Out dialog, which lets you check out all files in the project from source control.

    When you need to work on any of the Analyzer project files, you can check them out. Checking out files means to copy the latest source control files to your local Analyzer project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out.

    You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.

  • Get Latest Version All Opens the Get Latest Version dialog, which lets you "get" all files in the project from source control.

    After you bind a Analyzer project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Analyzer project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out.

    You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.

  • Update All Opens the Get Latest Version dialog, which lets you update files from source control.

    After you bind a Analyzer project to a Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Analyzer project.

    You will see this option if your project is bound to Subversion.

  • Undo Check Out All Opens the Undo Check Out dialog, which lets you reverse the check-out of all files in the project.

    If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files.

    You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

  • Revert All Opens the Revert dialog, which lets you return files to their last known state.

    If you have modified files from source control but do not want to keep your modifications, you can use the "Revert" option instead of committing the files. While committing the file would save your changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control.When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved.

    You will see this option if your project is bound to Git, Perforce, or Subversion.

  • Pull Opens the Select Remote for Pull dialog, which lets you select the remote repository from which you will download remote files.

    After you select the repository you want to pull from, the remote files are retrieved from the repository and downloaded to your local project. If necessary, Analyzer will perform a commit before pulling your files.

    You will see this option if your project is bound to Git.

    See Pulling Files from a Remote Repository—Git.

  • Push Opens the Select Remote for Push dialog, which lets you select the remote repository to which you will upload your local commits.

    After you select the repository you want to push to, your files are sent to the remote repository. If necessary, Analyzer will perform a commit before pushing your files.

    You will see this option if your project is bound to Git.

    See Pushing Files to a Remote Repository—Git.

  • Synchronize Opens the Select Remote for Synchronize dialog, which lets you select the remote you want to use for a pull and push of files.

    After you select the repository, Analyzer pulls the remote files from the Git repository and merges them with your local database. Then Analyzer pushes your local changes back to the remote Git repository. If necessary, Analyzer will perform a commit before synchronizing your files.

    You will see this option if your project is bound to Git.

  • Disconnect/Reconnect Disconnects the source control network so you can work offline. You can reconnect at any time.

    You will see this option if your project is bound to TFS, Perforce, or Subversion.

  • Network Settings Opens the Network Settings dialog, which lets you view and modify source control network settings from Flare.

    You will see this option if your project is bound to Git or Subversion.

• Add Opens the Add File(s) dialog, which lets you add the selected files to the integrated source control application. When working in a project that is connected to source control, there may be occasions when you have files in your local copy of the project that are not yet part of the source control copy. For example, when you add a new topic in your local copy of the project, that file will not be included in the source control copy of the project until you add it.

  You will see this option for all source control providers.

• Check In Opens the Check In dialog, which lets you check files into source control. When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control.

  You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

• Commit Opens the Commit dialog, which lets you commit files into source control.

  When you are finished editing files, you can commit them to source control. If you are working with Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote.

  If you are working with Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine.

  You will see this option if your project is bound to Git or Subversion.

• Submit Opens the Submit dialog, which lets you submit files into source control.

  When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control.

  You will see this option if your project is bound to Perforce.

• Check Out Opens the Check Out dialog, which lets you check out files from source control.

  When you need to work on any of the Analyzer project files, you can check them out. Checking out files means to copy the latest source control files to your local Analyzer project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out.

  You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.

• Lock Opens the Lock dialog, where you can select files you want to lock. If your project is bound to Subversion, you can steal locks from another user's locked files using this dialog. When you are working, you may want to lock the files you have modified. Locking a file does not prevent other users from modifying the file. However, no one else can commit a file that you have locked until you unlock the file. If your project is bound to Subversion, you can steal a lock from another user if you need to commit a locked file while they are working on it. Likewise, another user can steal a lock on a file you have locked.

  You will see this option if your project is bound to Perforce or Subversion.

• Unlock Opens the Unlock dialog, where you can select files you want to unlock. If you have locked a file, you should unlock it when you are done modifying it. Other users can modify the file while you have it locked, but they cannot submit a locked file until you unlock it. To help prevent file conflicts and make sure that everyone on your team has the most current version of the file, you should unlock and submit the file when you are finished working on it.

  You will see this option if your project is bound to Perforce or Subversion.

• Get Latest Version Opens the Get Latest Version dialog, which lets you "get" files from source control.

  After you bind a Analyzer project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Analyzer project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out.

  You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.

• Update Opens the Get Latest Version dialog, which lets you update files from source control.

  After you bind a Analyzer project to a Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Analyzer project.

  You will see this option if your project is bound to Subversion.

• Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files.

  If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files.

  You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

• Revert Opens the Revert dialog, which lets you return files to their last known state.

  If you have modified files from source control but do not want to keep your modifications, you can use the "Revert" option instead of committing the files. While committing the file would save your changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control.

  When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved.

  You will see this option if your project is bound to Git, Perforce, or Subversion.

• Show Differences Opens a window pane that lets you view the content and code differences for files. If you select a single file and choose this option, the differences between the local version of the file and the source control version of the file are shown. If you select two files and choose this option, the differences between those two files are shown.

  You will see this option for all source control providers.

• View History Opens the History dialog, which lets you view the history of a particular source control file, including all of the occasions when the file has been checked in. You can then use the dialog to view the differences between older versions of the file or roll back to a particular version.

  You will see this option for all source control providers.

• Request Check In Opens the Send Request Check-In Message Dialog, which lets you ask another user to check in the selected files so that you can edit them.

  If you discover that another user already has that file checked out, you can automatically send a request to that user to check in the file. This is a completely automated process involving instant messaging or email. Not only are the messages sent to the appropriate individuals automatically, but the mechanisms for checking in and checking out the necessary files are built in to those messages. This means that you and the other authors on your team do not need to hunt down the correct files manually.

  You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

• Request View File Opens the View File Request dialog, which lets you ask another user to view the selected file.

  If you have finished working on a file and want another user to review it, you can use the "Request View File" option. You can send an instant message or email to the other user with a message. That individual can then quickly open the specified file and send you comments about it.

  You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.

• Undelete Undeletes a file, allowing you to add it to source control. See Undeleting Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.
• Refresh Refreshes the window pane so that the latest information is shown. You will see this option for all source control providers.
• Pending Changes Opens the Pending Changes window pane, which displays files in the project that are pending check in (if the project is integrated with a source control application). In other words, you can use this window pane to see which files you have checked out, which files have been created but not yet added to source control, which files other users have checked out, and which files are out of date.  For more information see the Flare online Help. You will see this option for all source control providers.

Opens the Reports window pane, which lets you generate custom reports based on the information contained in your project, for just about any type of information that MadCap Analyzer captures. In addition, you can design the look and feel of reports, save them for future access, and open them in a browser window (where you can print them). See About Reports.

Opens the File Issues Viewer, where you can send selected files to the in order to see any issues associated with them. You can use the File List window pane to quickly add many files to this Viewer, or you can add files one at a time from within the user interface. See Viewing Issues for Specific Files.

Opens the Variable Suggestions window pane, which lets you view regular text that matches existing variables in your project, and then quickly convert these occurrences to variables. You can also double-click a row to open the topic in question, with the potential variable text highlighted. See Viewing Variable Suggestions.

Opens the Snippet Suggestions window pane, which lets you view content that matches existing snippets in your project, and you can quickly convert these occurrences to snippets. You can also double-click a row to open the topic in question, with the potential snippet content highlighted. See Viewing Snippet Suggestions.

Opens the Replace Local Style Suggestions window pane, which lets you view the places in your project where you have used local formatting. MadCap Analyzer suggests that you replace these instances of formatting with existing styles in your stylesheet that match the formatting that you have applied manually. This is different from a new style suggestion in the following way: With a new style suggestion, the properties in the tag do not match an existing style exactly; therefore, Analyzer suggests that you create a new style. On the other hand, if you make formatting changes that happen to result in an exact match to all of the properties in an existing style, Analyzer suggests that you replace the formatting with that style (rather than creating a new style). See Viewing Local Style Suggestions.

Opens the Markup Suggestions window pane, where you can search for places in your project where the XHTML markup (code) can be improved (e.g., empty tags, CDATA tags, empty attributes, excessive spaces). You can click the "Apply" button to automatically apply the suggestions to the selected files. You can click the "Search Properties" button to customize which types of issues to display in the window pane. You can double-click a row to open the topic or other file in the Analyzer interface. You can also select the row and click File > Send to Flare to open the file in the Flare project. See Viewing and Applying Markup Suggestions.

Opens the Undefined Glossary Term Links window pane, which lets you view a list of all files where you have glossary term links inserted into content, but those glossary terms do not appear in any of your glossary files. This might occur, for example, if you have created a new term in a glossary and then inserted that term into a topic as a glossary term link. Later, you remove that term from the glossary. You now have a glossary term link in a topic, but the term no longer exists in the glossary. Therefore, a problem exists. You need to either remove the glossary term link from the content, or you need to add the term to the glossary again. From the Undefined Glossary Term Links window pane, you can quickly unbind or rename multiple glossary term link occurrences in a single batch, add a new glossary term, or map the undefined term to an existing glossary term. See Viewing Undefined Glossary Term Links.

Opens the Undefined Condition Tags window pane, which lets you view a list of all files where you have condition tags in the content, but those condition tags have not been defined. This might occur, for example, if you have applied a condition tag in a topic and then later change the name of the tag or condition tag set. The old tag or set name is still used at the location where it was previously applied in the topic. Therefore, a problem exists. From the Undefined Condition Tags window pane, you can open the file in question and fix the undefined condition tag. You can also quickly rename or remove multiple condition tag occurrences in a single batch, add the undefined tag to the project, or map the undefined tag to an existing condition tag. See Viewing Undefined Condition Tags.

Opens the Undefined Styles window pane, which lets you view a list of all files where you have style classes applied to content, but those styles have not been defined. This might occur, for example, if you have created a new style class and applied it to a paragraph in a topic. Later, you remove that style class from the stylesheet. Therefore, you now have a style in a topic that is no longer defined in the stylesheet. You need to either apply a different, existing style class to that content, or you need to add the style class to the stylesheet again. You can also quickly rename or remove multiple style occurrences in a single batch, add the undefined style to the project, or map the undefined style to an existing style. See Viewing Undefined Styles.

Lets you select a font type (e.g., Arial, Times New Roman), applying it to the content selected in the topic.

Applies bold typeface to the content selected in the topic.

Underlines the content selected in the topic.

Lowers the selected content in the topic below the normal line of text (e.g., X₂).

Removes local formatting in a selection or even an entire topic. See Removing Inline Formatting.

Lets you choose and apply a color to the background of the selected content.

Aligns the selected content to the left.

Aligns the selected content to the right.

.Resets the alignment of the selected text to the default (inherited) setting.

Lets you shift indented content to the left, thus "outdenting" it.