31_Section16_Wrap_up.ppt

WRAP-UP What’s in this section: Build Files ADAMS/View Startup Files BUILD FILES Files that read in (or create) the various components of a customized interface are typically called “build” files. We highly recommend that you organize all types of GUI customization objects in subdirectories for organization and easy access. Sample build file: ADAMS/VIEW STARTUP FILES Startup files Startup files are files that ADAMS/View searches for and loads automatically if they exist. The following are the types of ADAMS/View startup files. They are listed in the order in which ADAMS/View searches for them: Aview.bin Used to save a customized ADAMS/View environment in binary format. Used to store the state of a specific modeling session. AviewBS.cmd - Preferences that you set. Before Startup (BS) means that ADAMS/View reads this command file before it reads other startup files. ADAMS/VIEW STARTUP FILES (CONT.) Aview.cmd - Contains commands for starting ADAMS/View. This file tends to be more model/project specific. AviewAS.cmd - Preferences that you set. After Startup (AS) means that ADAMS/View reads this command file after it reads other startup files. The Aview.bin file is unique when compared to the other startup files. This is because it is always read in. By default, this file is located in the install/aview directory and will load in the default ADAMS/View session. ADAMS/View will open the Aview.bin file that it finds first. ADAMS/VIEW STARTUP FILES (CONT.) Example uses: You can use the startup files to: Automatically customize your interface (for example, menus, buttons, and dialog boxes) Speed up the file-import/open process Modify your ADAMS/View environment (for example, lighting features, layouts, and creating custom views) ADAMS/VIEW STARTUP FILES (CONT.) Locations: ADAMS/View will read in the first startup file it encounters with the correct name (Aview.bin, AviewBS.cmd, Aview.cmd, and so on). ADAMS/View searches first for these files in your current working dire