Keynote Manager Header

Settings

Preferences
  • Use Last Keynote File at Startup: Checking this option will automatically reload the last file that was open when Keynote Manager is opened. This is recommended for those working primarily on one project. Those working on multiple projects should consider un-checking it in order to avoid waiting for the load process to complete, only to change the file and have to wait again.
  • Automatically Reload Keynotes: This option eliminates the need to manually reload your file when the keynote file changes. This can take some time but is recommended for instant save mode as it reduces the chance of one user accidentally overwriting changes by another user.
  • Save Mode
    • Instant Save - This option allows multiple users to edit the file simultaneously and is recommended where multiple project participants need to edit the file at the same time. It is important to note that when another user changes the file Keynote Manager's background will turn yellow signifying that the file needs to be reloaded. It is important to reload before making further changes or to turn on automatic reload.
    • Manual Save - This is a standard file editing mode where only one user can edit the file at a time. This mode is recommended for users or offices where there is only one user authorize to change the keynote file.
  • Default Directory: This option allows the user to set the default location for file open and save operations. When using the open command or creating a new file, the dialog box will start at this location. This allows easy definition of a 'projects' directory as a base to avoid having to re-browse through several folders.
  • Keynote Font: This option allows the user to select a font and color to display and print the keynotes. As some fonts have different appearances and special characters, it is recommended that this font be set to match the font that Revit will be using to print the keynotes so that the appearance in Revit will be consistent with the appearance in Keynote Manager.
  • Allow Usage Reporting: If checked, Keynote Manager will submit usage reports to Revolution Design when it shuts down. No personally identifiable information is collected, only data about the usage of the program. This data is used to help Revolution Design determine the most used features and the overall use patterns of the program, please consider leaving it on.
  • Check for Updates on Startup: If checked, Keynote Manager will automatically check for updates when it is started and notify the user of any new updates. If unchecked Keynote Manager will not check for updates on startup (user can still check for updates manually).
Master Files

Keynote Manager allows you to create new project keynote files based on any master text file you define here. You may define as many as you like, and you will be able to create new files based on these files by going to "File->New Keynote File Based on:" in the main Keynote Manager interface. You can also insert keynotes from a master file into your current file without the need to browse to find it.

Editing
  • Spell Check
    • User Dictionary: This is the path to the primary user dictionary. This is the dictonary to which words will be added when 'Add to Dictonary' is pressed on the spell checking palette. By default, this points to the user dictionary instlled with the product but this location may be changed to a common network directory if desired.
    • Revit Dictionary: Revit also uses dictionary files that are more specific to the AEC industry and Keynote Manager allows you to use your Revit dictionary in addition to the user dictionary. Keynote Manager automatically finds available Revit dictionaries and prompts you for selection.
  • Automatically Change Casing: This option allows you to set the automatic casing for new & edited keynotes. Keynotes can be set to default to upper, lower, sentence, title case, or none. Note that casing only applies to the description field, any letters in the keynote number will remain as is.
Backups

Keynote Manager will store up to 999 backups of each keynote file & comment file you open with it. Files are stored on startup, shutdown, load, and at a specified time interval if the option is selected in the settings dialog. Backups are stored on a per user basis at "*Applilcation Data*\Revolution Design\Keynote Manager\Backups" and are the original file name followed by the date and time they were saved.

Note also that these backups are on the local drive in the users application data folder, so they are user specific. Thus, the file is backed up on the computer of each team member who edits it. This creates a dispersed backup system that allows very reliable restoration of a lost or damaged keynote file to a recent state.

Deployment

Keynote Manager settings are stored in an easy to use xml file to assist BIM managers and IT people in deploying default settings to their users. In order to deploy settings to users, the Keynote Manager_Settings.xml must be deployed to the following location:

C:\Users\*username*\AppData\Roaming\Revolution Design\Keynote Manager\*version*\Keynote Manager_Settings.xml

In the above path *username* is your windows login name and *version* is the version of Keynote Manager (i.e. 12_5 for version 12.5).*

The recommended method for creating this file correctly is to load Keynote Manager on a sample machine and set the settings to desired values through the settings dialog. This will create the user settings file on that system, which can then be deployed to other machines.

The settings file may also be deployed paritally complete. If the BIM manager wishes only to deploy master files to the users and leave the remaining settings as default, simply delete all other settings from the file before deployment. Keynote Manager will read the deployed values present and fill in default values for the remaining items.

*Note that there is also a file named 'KMInternal_Settings.xml' in the same folder. This file stores internal Keynote Manager settings such as window positions and sizes and should not be deployed to users.