1. WS16-1 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 WRAP-UP

2. WS16-2 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation

3. WS16-3 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Problem statement u Package the files that build the new interface so that they are organized and upwardly compatible.

4. WS16-4 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Organizing the file system structure u In this section, you will organize your file system structure such that all files necessary to build the custom interface are easily accessible. To organize the file system structure: 1. From the mod_16_disk directory, create the following directories: l dboxes l menu l model See the instructor if you need help with this.

5. WS16-5 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP 2. Copy files from Workshop 15 – Working with the Dialog Box Builder to the new directory structure. Ensure that the command files representing the three dialog boxes (design_layout, Simulate, and review) are placed in the new dboxes directory, and that the command file representing the model is placed in the new model directory. For now, the menu directory will be empty. 3. Rename the model file from disk_start_3.cmd to disk_final.cmd.

6. WS16-6 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Creating a build file u You will now create a build text file that essentially builds the custom interface and reads in the model. Remember that the dialog boxes were stored and saved in a user-created library. If the library does not exist, reading in the command files that build the dialog boxes will not work.

7. WS16-7 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n To create a build file: 1. Create a text file called build.cmd in the mod_16_disk directory that builds the ADAMS/View interface to contain the model and the three dialog boxes. !--- Read in the command file file command read file=”./model/disk_final.cmd”\ !--- Create the library library create library_name=.my_cust !--- Import the dialog boxes file command read file=”./dboxes/design_layout.cmd”

8. WS16-8 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP 2. Start ADAMS/View from the mod_16_disk directory. 3. Import the file called build.cmd from the mod_16_disk directory to build the custom interface. If errors are generated, debug the build command file until you no longer get errors when reading this file into a fresh session of ADAMS/View. 4. Update the build command file, build.cmd, so that it also displays the dialog boxes. You should be able to do this on your own. If you need help with the command syntax, display one of the dialog boxes. (From the Tools menu, point to Dialog Box, select Display, and then review the command used behind the scenes by displaying the ADAMS/View Command Window.) 5. Test the new build file from a fresh ADAMS/View session.

9. WS16-9 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Creating a menu u In this section, you will create a command file that builds a menu to easily display the custom dialog boxes. To create a menu: 1. Create a command file called disk_menu.cmd in the mod_16_disk/menu directory that creates menus to display the dialog boxes. !--- Create a custom menu for the disk transfer mechanism. interface menu create & menu_name =.gui.main.mbar.disk & label = “Disk Transfer” interface push create & push_button_name =.gui.main.mbar.disk.layout & label = “Design Layout” & command = “interface dialog_box display dialog_box=.my_cust.design_layout

10. WS16-10 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP 2. Update the build command file so that it reads in the command file that will build the menu. Because you will now have a custom menu that will display these dialog boxes, you can comment out or delete the commands that display the custom dialog boxes. 3. Test the new build file from a fresh ADAMS/View session.

11. WS16-11 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Swapping a dialog box u In this section, you will learn how to swap one dialog box for another one using a build command file.

12. WS16-12 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n To swap a dialog box: 1. Copy the design_layout dialog box command file that was used in Workshop 1 - Introduction (mod_01_intro/dboxes/design_layout_dbox.cmd) to the mod_16_disk/dboxes directory. 2. Rename this file to design_layout_advanced.cmd. This dialog box is slightly more advanced because it allows the user to also control Point 4, instead of just Points 1 and 2. 3. Update the build file so that it replaces the existing design_layout dialog box with the new one. You have now learned how to put together a custom interface containing models, dialog boxes, menus, libraries, and potentially macros into a clean and organized structure. This method will also ensure that your customization work is upwardly compatible with future versions of ADAMS/View.

13. WS16-13 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation WORKSHOP 16 - WRAP-UP n Module review 1. If dialog boxes were created in the.gui library and the session was saved in binary file format in ADAMS/View version 12.0, would they exist in version 2005? _____________________________________________________ What if they were created in a user-created library? _____________________________________________________ 2. If your custom interface included a macro stored in a subdirectory called macros, what build file command(s) would you use to read in the macro? _____________________________________________________

14. WS16-14 ADM704-705, Workshop 16, August 2005 Copyright  2005 MSC.Software Corporation