Home

ABAQUS GUI Toolkit User's Manual

1. APPENDIX B COLORS AND RGB VALUES String RGB value LightYellow1 FXRGB 255 255 224 LightYellow2 FXRGB 238 238 209 LightYellow3 FXRGB 205 205 180 LightYellow4 FXRGB 139 139 122 LimeGreen FXRGB 50 205 50 Linen FXRGB 250 240 230 Magenta FXRGB 255 0 255 Magental FXRGB 255 0 255 Magenta2 FXRGB 238 0 238 Magenta3 FXRGB 205 0 205 Magenta4 FXRGB 139 0 139 Maroon FXRGB 176 48 96 Maroonl FXRGB 255 52 179 Maroon2 FXRGB 238 48 167 Maroon3 FXRGB 205 41 144 Maroon4 FXRGB 139 28 98 Medium Aquama FXRGB 102 205 170 rine MediumBlue FXRGB 0 0 205 Medium Orchid FXRGB 186 85 211 MediumOrchid1 FXRGB 224 102 255 MediumOrchid2 FXRGB 209 95 238 MediumOrchid3 FXRGB 180 82 205 MediumOrchid4 FXRGB 122 55 139 MediumPurple FXRGB 147 112 219 MediumPurple1 FXRGB 171 130 255 MediumPurple2 FXRGB 159 121 238 MediumPurple3 FXRGB 137 104 205 APPENDIX B COLORS AND RGB VALUES String RGB value MediumPurple4 MediumSeaGreen MediumSlateBlue Medium Spring Green MediumTurquoise MediumVioletRed MidnightBlue MintCream MistyRose MistyRose1 MistyRose2 MistyRose3 MistyRose4 Moccasin NavajoWhite NavajoWhite1 NavajoWhite2 NavajoWhite3 NavajoWhite4 Navy NavyBlue None OldLace OliveDrab OliveDrab1 OliveDrab2 OliveDrab3 FXRGB 93 71 139 FXRGB 60 179 113 FXRGB 123 104 238 FXRGB 0 250 154 FXRGB 72 209 204 FXRGB 199 21 133 FXRGB 25 25 112
2. FXButton gb Button 3 opts LAYOUT_SIDE_LEFT BUTTON_NORMAL 4 10 LAYOUT EXAMPLES 2 n 3 a Figure 4 10 Adding a third button on the left side at the top of the layout cavity Figure 4 11 shows the final configuration of the three buttons eC3Orcc SLLLLLLLLSALLS SSS L GE A Button 1 G Button 2 2 Button 3 y Figure 4 11 The final configuration of the buttons Example 2 The second example illustrates how you can use nondefault layout hints The example starts by using the default hints to position a button on top of the available space and on the left gb FXGroupBox p FXButton gb Button 1 iif Space available for remaining children SSN Figure 4 12 Creating a button on the left side and at the top of the layout cavity The example then positions a second button on the right side on the bottom of the layout cavity FXButton gb Button 2 opts LAYOUT_ SIDE BOTTOM LAYOUT_RIGHT BUTTON NORMAL 4 11 LAYOUT EXAMPLES Figure 4 13 Adding a second button on the right side at the bottom of the layout cavity F am 2 an places a third button on the bottom of the available space and centered in the Y directi G n i G opts LAYOUT_SIDE_BOTTOM LAYOUT_CENTER_ X BUTTON_NORMAL Figure 4 14 Adding a third button in the center at the bottom of the layout cavi Figure 4 15 shows the final configuration of the three buttons 4 12 TIPS FOR SPECIFYING LAYOUT HIN
3. Ifa mode needs to perform drawing or highlighting in the current viewport the mode must be a procedure mode Because ABAQUS CAE highlights objects that the user picks any mode that requires the user to pick in the viewport must also be a procedure mode Procedure modes ensure that only one procedure at a time has control over the scene in the current viewport If two different procedures could highlight different portions of the model for different purposes the resulting display would be confusing and ambiguous 7 2 Mode processing Modes are typically activated by a button in the GUI Once a mode is activated it is responsible for gathering user input processing the input sending a command and performing any error handling associated with the mode or the commands it sends This section describes how modes are processed The following topics are covered e The mode processing sequence Section 7 2 1 e Activating a mode Section 7 2 2 MODE PROCESSING e Step and dialog box processing Section 7 2 3 e Command processing Section 7 2 4 e Work in progress Section 7 2 5 e Command error handling Section 7 2 6 7 2 1 The mode processing sequence During the input gathering process the mode allows you to perform some intermediate error checking For example if the user is supposed to enter a value between zero and one but enters a value outside this range you can flag the error before continuing to c
4. FRAME GROOVE LAYOUT FILL X hf FXHorizontalFrame gb 0 0 0 0 0 0 0 0 0 DATA DIALOG BOXES FXLabel hf Drag mode FXRadioButton hf Fast wireframe form dragModekw FAST getId FXRadioButton hf As is form dragModeKw AS IS getId FXCheckButton gb Auto fit after rotations form autoFitKw Figure 5 7 shows the Graphics Options dialog box generated by the example script WE Graphics Options Eq r Hardware Driver OpenGL x11 M Use double buffering M Use display lists 7 View Manipulation Drag mode Fast wireframe As is I Auto fit after rotations Defaults Cancel Figure 5 7 Graphics Options data dialog box 5 6 5 Transitions Transitions provide a convenient way to change the GUI state in a dialog box Transitions are used to stipple widgets or to rotate regions when some other control in the dialog box is activated If the behavior in your dialog box can be described in terms of simple transitions you can use the addTransition method to produce the state changes Transitions compare the value of a keyword with a specified value If the operator condition is met a message is sent to the specified target object Transitions have the following prototype addTransition keyword operator value tgt sel ptr For example when the user selects Wireframe as the render style in the Part Display Options dialog box ABAQUS CAE does the following e Stippl
5. Figure 3 32 Setting colors for table items 3 31 TABLE WIDGET 3 6 13 Sorting You can set a column in a table to be sortable If a column is set to be sortable and the user clicks on its heading a graphic will be displayed in the heading that shows the order of the sort You must write the code that performs the actual sorting in the table the table itself provides only the graphical feedback in the heading cell For example class MyDB AFXDataDialog def Handle clicks in the table FXMAPFUNC self SEL_CLICKED self ID TABLE MyDB onClickTable Create a table vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 self sortTable AFXTable vf 4 3 4 3 self self ID_TABLE AFXTABLE NORMAL AFXTABLE EDITABLE self sortTable setLeadingRows 1 self sortTable setLeadingRowLabels Name tX tY self sortTable setColumnSortable 1 TRUE self sortTable setColumnSortable 2 TRUE onClickTable self sender sel ptr status x y buttons self sortTable getCursorPosition column self sortTable getColumnAtX x row self sortTable getRowAtY y Ignore clicks on table headers if row 0 or column return values index 1 for row in range 1 self sortTable getNumRows values append self sortTable getItemFloatValue row column index 3 32 MISCELLANEOUS WIDGETS index 1 values sort if self sortTable getColumnSortOrder column AFXTable SO
6. GUI Toolkit User s Manual ii ABAQUS Version 6 5 Trademarks and Legal Notices CAUTIONARY NOTICE TO USERS This manual is intended for qualified users who will exercise sound engineering judgment and expertise in the use of the ABAQUS Software The ABAQUS Software is inherently complex and the examples and procedures in this manual are not intended to be exhaustive or to apply to any particular situation Users are cautioned to satisfy themselves as to the accuracy and results of their analyses ABAQUS Inc will not be responsible for the accuracy or usefulness of any analysis performed using the ABAQUS Software or the procedures examples or explanations in this manual ABAQUS Inc shall not be responsible for the consequences of any errors or omissions that may appear in this manual ABAQUS INC DISCLAIMS ALL EXPRESS OR IMPLIED REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OF THE CONTENTS OF THIS MANUAL IN NO EVENT SHALL ABAQUS INC OR ITS THIRD PARTY PROVIDERS BE LIABLE FOR ANY INDIRECT INCIDENTAL PUNITIVE SPECIAL OR CONSEQUENTIAL DAMAGES INCLUDING WITHOUT LIMITATION DAMAGES FOR LOSS OF BUSINESS PROFITS BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION EVEN IF ABAQUS INC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES The ABAQUS Software described in this manual is available only under license from ABAQUS Inc and may be used or reproduced
7. General purpose layout managers Section 4 5 e Row and column layout manager Section 4 6 e Resizable regions Section 4 7 e Rotating regions Section 4 8 e Tab books Section 4 9 e Layout hints Section 4 10 e Layout examples Section 4 11 e Tips for specifying layout hints Section 4 12 4 1 An overview of layout managers A layout manager places its children in a certain arrangement in its interior Layout managers use a combination of layout hints and packing styles to determine how to place and size their children Layout managers in the ABAQUS GUI Toolkit calculate relative sizes and relative positions as opposed to absolute coordinates This relative approach accounts automatically for changes such as different font sizes and window resizing The following layout managers are available in the ABAQUS GUI Toolkit FXHorizontalFrame Arranges widgets horizontally For more information see Horizontal and vertical frames Section 4 3 FXVerticalFrame Arranges widgets vertically For more information see Horizontal and vertical frames Section 4 3 AFXVerticalAligner Vertically aligns the first child of its children For more information see Vertical alignment for composite children Section 4 4 PADDING AND SPACING FXPacker Arranges widgets in a general manner For more information see General purpose layout managers Section 4 5 FXTopWindow S
8. None menu AFXMenuCommand self menu amp Item 1 None mode 1 AFXMode ID_ACTIVATE subMenu AFXMenuPane self AFXMenuCascade self menu amp Submenu None subMenu AFXMenuCommand self subMenu amp Subitem 1 None mode 2 AFXMode ID_ACTIVATE Toolbar items group AFXToolbarGroup self icon FXXpmIcon getAFXApp iconDatal AFXToolButton group tTool Tip icon mode 1 AFXMode ID_ACTIVATE Toolbox items group AFXToolboxGroup self icon FXXPMIcon getAFXApp iconData2 AFXToolButton group tTool Tip icon mode 1 AFXMode ID_ACTIVATE popup AFXPopup self getAFXApp getAFXMainWindow GUI MODULE EXAMPLE AFXFlyoutItem popup tFlyout Button 1 squarelcon mode _1 AFXMode ID ACTIVATE AFXFlyoutItem popup tFlyout Button 2 circlelcon mode 2 AFXMode ID ACTIVATE AFXFlyoutItem popup tFlyout Button 3 trianglelcon mode _ 3 AFXMode ID ACTIVATE AFXFlyoutButton group popup Register toolsets self registerToolset MyToolsetGui GUI_IN_MENUBAR GUI_IN_TOOL_PANE Pr nnn nn nn nn nn nnn nnn nn nnn WN NNN RRA A def getKernelInitializationCommand self return import myModule Instantiate the module MyModuleGui 8 2 1 Deriving a new module class To create your own module GUI you begin by deriving a new class from the AFXModuleGui base class Alternatively if there is another module GUI class that provides most of the f
9. Section 1 1 e Prerequisites for using the ABAQUS GUI Toolkit Section 1 2 e ABAQUS GUI Toolkit basics Section 1 3 e Organization of the ABAQUS GUI Toolkit User s Manual Section 1 4 What can I do with the ABAQUS GUI Toolkit There are many ways to customize ABAQUS products e User subroutines allow you to change the way ABAQUS Standard and ABAQUS Explicit compute analysis results e Environment files allow you to change various default settings e Kernel scripts allow you to create new functions to perform modeling or postprocessing tasks e GUI scripts allow you to create new graphical user interfaces Information on user subroutines and environment files can be found in the ABAQUS Analysis User s Manual Information on kernel scripts can be found in the ABAQUS Scripting User s Manual GUI scripts are described in this manual The ABAQUS GUI Toolkit provides programming routines that allow you to create or modify components of the graphical user interface GUI The toolkit allows you to do the following e Create anew GUI module A GUI module is a grouping of similar functionality such as the Part module in ABAQUS CAE e Create a new GUI toolset A GUI toolset is similar to a GUI module in that it groups similar functionality but it generally contains more specific functionality that may be used by one or more GUI modules The Datum tools in ABAQUS CAE are an example of a GUI toolset e Create new dialog b
10. 13 FXRGB 127 127 127 FXRGB 130 130 130 FXRGB 133 133 133 FXRGB 135 135 135 FXRGB 138 138 138 FXRGB 140 140 140 FXRGB 143 143 143 FXRGB 145 145 145 FXRGB 148 148 148 FXRGB 150 150 150 FXRGB 15 15 15 FXRGB 153 153 153 FXRGB 156 156 156 FXRGB 158 158 158 FXRGB 161 161 161 FXRGB 163 163 163 FXRGB 166 166 166 FXRGB 168 168 168 FXRGB 171 171 171 FXRGB 173 173 173 FXRGB 176 176 176 B 8 APPENDIX B COLORS AND RGB VALUES String RGB value Gray7 FXRGB 18 18 18 Gray70 FXRGB 179 179 179 Gray71 FXRGB 181 181 181 Gray72 FXRGB 184 184 184 Gray73 FXRGB 186 186 186 Gray74 FXRGB 189 189 189 Gray75 FXRGB 191 191 191 Gray76 FXRGB 194 194 194 Gray77 FXRGB 196 196 196 Gray78 FXRGB 199 199 199 Gray79 FXRGB 201 201 201 Gray8 FXRGB 20 20 20 Gray80 FXRGB 204 204 204 Gray81 FXRGB 207 207 207 Gray82 FXRGB 209 209 209 Gray83 FXRGB 212 212 212 Gray84 FXRGB 214 214 214 Gray85 FXRGB 217 217 217 Gray86 FXRGB 219 219 219 Gray87 FXRGB 222 222 222 Gray88 FXRGB 224 224 224 Gray89 FXRGB 227 227 227 Gray9 FXRGB 23 23 23 Gray90 FXRGB 229 229 229 Gray91 FXRGB 232 232 232 Gray92 FXRGB 235 235 235 Gray93 FXRGB 237 237 237 Gray94 FXRGB 240 240 240 B 9 APPENDIX B COLORS AND RGB VALUES String RGB value Gray95 FXRGB 242 242 242 Gray96 FXRGB 245 245 245 Gray97 FXRGB 247 247 247 Gray98 FXRGB 250 250 250 Gray99 FXRGB 252 252 252 Green FXRGB 0
11. ABAQUS CAE exhibits this behavior in manager dialogs that contain more than one column The following statements creates a table with default settings Tables do not draw a frame around their border Therefore add a frame widget with zero padding vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 Figure 3 22 A table created with default settings 3 6 2 Rows and columns The table supports leading rows and columns Leading rows and columns are displayed as buttons using a bold text Leading rows are displayed at the top of the table and leading columns are displayed on the left side of the table The number of rows and columns that you specify in the table constructor are the total number of rows and columns including the leading rows and columns By default the table has no leading rows or columns you must set the leading rows and columns after the table is constructed using the appropriate table methods You can also specify the labels to be displayed in these rows and columns If you do not specify any labels for a leading row or column it will be numbered automatically You can set more than one label at once in a heading by using t to separate the labels in a single string By default no grid lines are drawn around items You can control the visibility of the horizontal and vertical grid lines individually by using the following table methods showHorizontalGrid TR
12. Aborted Including icons in table cells If you want to display a color button in a table you must set the type to COLOR If the table is editable the user can use the color button to change the color via the color selection dialog box The color button is a flyout button that can have up to three flyout items one for a specific color one for a default color and one for an as is color Refer to the Color Code dialog box in ABAQUS CAE to see examples of how these options may be used The options are specified using the flags in the following table Option flag Effect COLOR_INCLUDE_COLOR_ONLY COLOR_INCLUDE_AS IS Include only the color flyout item Include the as is flyout item 3 27 TABLE WIDGET Option flag Effect COLOR_INCLUDE_DEFAULT Include the default flyout item COLOR_INCLUDE_ALL Include all of the flyout items The following example shows how you can display color buttons in a table vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 AFXTABLE NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table setLeadingRowLabels Name tColor table setColumnType 1 AFXTable COLOR table setColumnColorOptions 1 AFXTable COLOR INCLUDE COLOR ONLY table setItemText 1 0 Part 1 table setItemText 2 0 Part 2 table setItemText 3 0 Part 3 table setItemColor 1 1 FF0000 table
13. The appendActionButton method has two prototypes appendActionButton buttonId appendActionButton text tgt sel The first version of the prototype creates a standard action area button as defined in Table 5 1 The second version of the prototype creates a button whose label is given as the text argument In addition the second version allows you to set the target and selector so that you can catch messages from this button and act accordingly The following statements show how you can create custom action area buttons class ActionAreaDB AFXDialog def _init self AFXDialog init self Action Area Example 2 0 DIALOG ACTIONS SEPARATOR FXLabel self Custom action area example dialog self appendActionButton Highlight self self ID_CLICKED_APPLY self appendActionButton self CANCEL Action Area Example 2 x Custom action area example dialog Highlight Cancel Figure 5 5 An example of a custom action area 5 5 6 Action button handling AFXDialog and AFXDataDialog provide some automatic handling of the messages that are sent when a button in the action area is clicked If you want to perform some actions other than those provided by the dialog box you must catch the messages sent by the action area buttons and write your own message handler For example if you want to take an action when the user clicks the Apply button in the dialog box you must catch the ID CLICKED APPLY SEL COMMAND mes
14. The button also supports a third Maybe or Some state The Maybe state is often used to represent a partial selection for example the AFXOptionTreeList widget makes use of the Maybe state You can set the Maybe state only programmatically the user cannot toggle the button to this state FXCheckButton parent This is an FXCheckButton M This is an FXCheckButton Figure 3 4 An example of a check button and a label from FXCheckButton 3 1 5 Radio buttons The FXRadioButton widget provides a one of many selection from a group of buttons FXRadioButton parent This is FXRadioButton 1 FXRadioButton parent This is FXRadioButton 2 FXRadioButton parent This is FXRadioButton 3 This is FXRadioButton 1 C This is FXRadioButton 2 C This is FXRadioButton 3 Figure 3 5 An example of radio buttons from FXRadioButton 3 1 6 Menu buttons A menu consists of the following LABELS AND BUTTONS e A menu title created by AFXMenuTitle e A menu pane created by AFXMenuPane e A menu command created by AFXMenuCommand The menu title resides in amenu bar and controls the display ofthe menu pane associated with the menu title The menu pane contains menu commands Menu commands are buttons that generally invoke some action A menu pane can also contain a cascading menu created by AFXMenuCascade A cascading menu provides submenus within amenu Figure 3 6 illustrates the components of a menu
15. This first example contains only one dialog box a subsequent example will extend this form to include multiple dialog boxes from abaqusGui import from plateDB import PlateDB class PlateForm AFXForm Ha ww w w w w w m a a m a m m a a a a a m m a a ay ay m m a a my y m m a a my y my ma a a y N y ma a def _ init self owner AFXForm init__ self owner self cmd AFXGuiCommand self Plate examples self nameKw AFXStringKeyword self cmd name TRUE self widthKw AFXFloatKeyword self cmd width TRUE self heightKw AFXFloatKeyword 7 7 FORM MODES self cmd height TRUE Ha ww w w w w w m m a m a m m m a a a a m m a a m ay m m a a my y m m a a my y m ma a e y N y ma aa def getFirstDialog self self cmd setKeywordValuesToDefaults return PlateDB self 7 3 2 Form constructor You begin writing a form mode by deriving a new class from AFXForm In the body of the AFXForm constructor you must call the base class constructor and pass in the owner which is the module or toolset GUI to which this form belongs You then define the commands and keywords that the mode will use The keywords are stored as members of the mode so that they can be accessed by dialog boxes Ifyou set registerQuery TRUE in the AFXGuiCommand constructor the mode will query the kernel object specified by the command when it is activated and will automatically set the values of the command s keywords For more informat
16. def __init_ self mw getAFXApp getAFXMainWindow self registerToolset mw myDtmGui GUI_IN_TOOL_PANE GUI_IN_TOOLBOX 10 2 The Help toolset The Help toolset contains special methods that allows you to add your own logo and copyright information to the Help On Version dialog box Customized applications must show the standard copyright information displayed by ABAQUS CAE or ABAQUS Viewer In addition you can customize the copyright information at the top of the On Version dialog box using the following methods e setCustomCopyrightStrings customCopyrightVersion customCopyrightInfo e setCustomLogolcon logoIcon For example from abaqusGui import 10 4 THE HELP TOOLSET from sessionGui import HelpToolsetGui from myIcons import class MyMainWindow AFXMainWindow def init__ self app windowTitle Add custom copyright info to the On Version dialog helpToolset HelpToolsetGui product getAFXApp getProductName major minor update getAFXApp getVersionNumbers prerelease getAFXApp getPrerelease if prerelease version s Version s s PRE s product major minor update else version s Version s s s product major minor update info Copyright 2003 nMy Company helpToolset setCustomCopyrightStrings version info icon FXXPMIcon app myIconData helpToolset setCustomLogolcon icon self registerHelpToolset helpToolset GUI_IN_MENUBAR A
17. etc Figure 11 1 An overview of GUI code e Instantiates a main window The main window is what the user sees when the application is first started and provides access to all of the application s functionality e Creates and runs the application Once the application is run it enters an event loop where it waits to react to user input such as the click of a mouse The following illustrates a typical startup script Note You can download this script and the files associated with it for example caeMainWindow py from the ABAQUS Process Automation Portal from abaqusGui import AFXApp import sys from caeMainWindow import CaeMainWindow Initialize the application object app AFXApp ABAQUS CAE ABAQUS Inc app init sys argv Construct the main window CaeMainWindow app Create the application and run it 11 2 INSTALLATION app create app run The first statement in the script imports the AFXApp constructor from the abaqusGui module which contains access to the entire ABAQUS GUI Toolkit The sys module is also imported since it is needed to pass arguments into the application s init method After the script imports the sys module it imports the main window constructor The next statements instantiate and initialize the application object The application object is discussed in more detail in The application object Section 12 1 The script then instantiates the main window The mai
18. getId self imageSizeKw AFXTupleKeyword cmd imageSize FALSE 1 2 AFXTUPLE_TYPE_FLOAT 6 4 9 Connecting keywords to widgets Keywords are used in the GUI by setting them as the targets of widgets The AFXDataDialog class takes a mode as one of its constructor arguments The dialog box uses the mode provided in the constructor to access the keywords stored in the mode In addition the dialog box uses the keywords as targets of widgets in the dialog In addition to a target a widget also has a message ID It is important that the appropriate ID be set for the keyword to operate in the proper mode value or option For more information see Data targets Section 6 4 6 In most cases a value of zero should be used for the message ID a value of zero indicates that the keyword should operate in value mode The table below summarizes the message ID usage with keywords and the following sections give examples for each type of keyword Keyword ID Description AFXIntKeyword 0 Keyword operates in value mode Use this when the keyword is connected to a text field list combo box or spinner gt 0 Keyword operates in option mode Use this when the keyword is connected to a radio button AFXFloatKeyword 0 Keyword operates in value mode AFXStringKeyword 0 Keyword operates in value mode AFXBoolKeyword 0 Keyword operates in value mode This keyword should be used only with widgets that allow only Boolean values such as F
19. 255 0 Green1 FXRGB 0 255 0 Green2 FXRGB 0 238 0 Green3 FXRGB 0 205 0 Green4 FXRGB 0 139 0 Green Yellow FXRGB 173 255 47 Grey FXRGB 190 190 190 Grey0 FXRGB 0 0 0 Greyl FXRGB 3 3 3 Grey10 FXRGB 26 26 26 Grey100 FXRGB 255 255 255 Grey11 FXRGB 28 28 28 Grey12 FXRGB 31 31 31 Grey 13 FXRGB 33 33 33 Grey14 FXRGB 36 36 36 Grey15 FXRGB 38 38 38 Grey16 FXRGB 41 41 41 Grey17 FXRGB 43 43 43 Grey18 FXRGB 46 46 46 Grey19 FXRGB 48 48 48 Grey2 FXRGB 5 5 5 Grey20 FXRGB 51 51 51 Grey21 FXRGB 54 54 54 APPENDIX B COLORS AND RGB VALUES String RGB value Grey22 FXRGB 56 56 56 Grey23 FXRGB 59 59 59 Grey24 FXRGB 61 61 61 Grey25 FXRGB 64 64 64 Grey26 FXRGB 66 66 66 Grey27 FXRGB 69 69 69 Grey28 FXRGB 71 71 71 Grey29 FXRGB 74 74 74 Grey3 FXRGB 8 8 8 Grey30 FXRGB 77 77 77 Grey31 FXRGB 79 79 79 Grey32 FXRGB 82 82 82 Grey33 FXRGB 84 84 84 Grey34 FXRGB 87 87 87 Grey35 FXRGB 89 89 89 Grey36 FXRGB 92 92 92 Grey37 FXRGB 94 94 94 Grey38 FXRGB 97 97 97 Grey39 FXRGB 99 99 99 Grey4 FXRGB 10 10 10 Grey40 FXRGB 102 102 102 Grey41 FXRGB 105 105 105 Grey42 FXRGB 107 107 107 Grey43 FXRGB 110 110 110 Grey44 FXRGB 112 112 112 Grey45 FXRGB 115 115 115 Grey46 FXRGB 117 117 117 Grey47 FXRGB 120 120 120 APPENDIX B COLORS AND RGB VALUES String RGB value Grey48 Grey49 Grey5 Grey5
20. FXRGB 139 136 120 Cyan FXRGB 0 255 255 Cyanl FXRGB 0 255 255 Cyan2 FXRGB 0 238 238 Cyan3 FXRGB 0 205 205 Cyan4 FXRGB 0 139 139 DarkBlue FXRGB 0 0 139 DarkCyan FXRGB 0 139 139 DarkGoldenrod FXRGB 184 134 11 DarkGoldenrod1 FXRGB 255 185 15 DarkGoldenrod2 FXRGB 238 173 14 DarkGoldenrod3 FXRGB 205 149 12 DarkGoldenrod4 FXRGB 139 101 8 DarkGray FXRGB 169 169 169 B 3 APPENDIX B COLORS AND RGB VALUES String RGB value DarkGreen DarkGrey DarkKhaki DarkMagenta DarkOliveGreen DarkOliveGreen1 DarkOliveGreen2 DarkOliveGreen3 DarkOliveGreen4 DarkOrange DarkOrange1 DarkOrange2 DarkOrange3 DarkOrange4 DarkOrchid DarkOrchid1 DarkOrchid2 DarkOrchid3 DarkOrchid4 DarkRed DarkSalmon DarkSeaGreen DarkSeaGreen1 DarkSeaGreen2 DarkSeaGreen3 DarkSeaGreen4 DarkSlateBlue DarkSlateGray FXRGB 0 100 0 FXRGB 169 169 169 FXRGB 189 183 107 FXRGB 139 0 139 FXRGB 85 107 47 FXRGB 202 255 112 FXRGB 188 238 104 FXRGB 162 205 90 FXRGB 110 139 61 FXRGB 255 140 0 FXRGB 255 127 0 FXRGB 238 118 0 FXRGB 205 102 0 FXRGB 139 69 0 FXRGB 153 50 204 FXRGB 191 62 255 FXRGB 178 58 238 FXRGB 154 50 205 FXRGB 104 34 139 FXRGB 139 0 0 FXRGB 233 150 122 FXRGB 143 188 143 FXRGB 193 255 193 FXRGB 180 238 180 FXRGB 155 205 155 FXRGB 105 139 105 FXRGB 72 61 139 FXRGB 47 79 79 APPENDIX B COLORS AND RGB VALUES String RGB value DarkSlateGray1 DarkSl
21. FXRGB 245 255 250 FXRGB 255 228 225 FXRGB 255 228 225 FXRGB 238 213 210 FXRGB 205 183 181 FXRGB 139 125 123 FXRGB 255 228 181 FXRGB 255 222 173 FXRGB 255 222 173 FXRGB 238 207 161 FXRGB 205 179 139 FXRGB 139 121 94 FXRGB 0 0 128 FXRGB 0 0 128 FXRGB 0 0 0 0 FXRGB 253 245 230 FXRGB 107 142 35 FXRGB 192 255 62 FXRGB 179 238 58 FXRGB 154 205 50 APPENDIX B COLORS AND RGB VALUES String RGB value OliveDrab4 FXRGB 105 139 34 Orange FXRGB 255 165 0 Orangel FXRGB 255 165 0 Orange2 FXRGB 238 154 0 Orange3 FXRGB 205 133 0 Orange4 FXRGB 139 90 0 OrangeRed FXRGB 255 69 0 OrangeRed1 FXRGB 255 69 0 OrangeRed2 FXRGB 238 64 0 OrangeRed3 FXRGB 205 55 0 OrangeRed4 FXRGB 139 37 0 Orchid FXRGB 218 112 214 Orchid FXRGB 255 131 250 Orchid2 FXRGB 238 122 233 Orchid3 FXRGB 205 105 201 Orchid4 FXRGB 139 71 137 PaleGoldenrod FXRGB 238 232 170 PaleGreen FXRGB 152 251 152 PaleGreen1 FXRGB 154 255 154 PaleGreen2 FXRGB 144 238 144 PaleGreen3 FXRGB 124 205 124 PaleGreen4 FXRGB 84 139 84 PaleTurquoise FXRGB 175 238 238 PaleTurquoisel FXRGB 187 255 255 PaleTurquoise2 FXRGB 174 238 238 PaleTurquoise3 FXRGB 150 205 205 PaleTurquoise4 FXRGB 102 139 139 PaleVioletRed FXRGB 219 112 147 APPENDIX B COLORS AND RGB VALUES String RGB value PaleVioletRed1 PaleVioletRed2 PaleVioletRed3 PaleVioletRed4 PapayaWhip PeachPuff PeachPuff1 PeachPuff2 PeachPuff3
22. FXRGB 255 228 196 Bisque2 FXRGB 238 213 183 Bisque3 FXRGB 205 183 158 Bisque4 FXRGB 139 125 107 Black FXRGB 0 0 0 APPENDIX B COLORS AND RGB VALUES String RGB value BlanchedAlmond FXRGB 255 235 205 Blue FXRGB 0 0 255 Bluel FXRGB 0 0 255 Blue2 FXRGB 0 0 238 Blue3 FXRGB 0 0 205 Blue4 FXRGB 0 0 139 BlueViolet FXRGB 138 43 226 Brown FXRGB 165 42 42 Brownl FXRGB 255 64 64 Brown2 FXRGB 238 59 59 Brown3 FXRGB 205 51 51 Brown4 FXRGB 139 35 35 Burlywood FXRGB 222 184 135 Burlywood1 FXRGB 255 211 155 Burlywood2 FXRGB 238 197 145 Burlywood3 FXRGB 205 170 125 Burlywood4 FXRGB 139 115 85 CadetBlue FXRGB 95 158 160 CadetBluel FXRGB 152 245 255 CadetBlue2 FXRGB 142 229 238 CadetBlue3 FXRGB 122 197 205 CadetBlue4 FXRGB 83 134 139 Chartreuse FXRGB 127 255 0 Chartreuse1 FXRGB 127 255 0 Chartreuse2 FXRGB 118 238 0 Chartreuse3 FXRGB 102 205 0 Chartreuse4 FXRGB 69 139 0 Chocolate FXRGB 210 105 30 APPENDIX B COLORS AND RGB VALUES String RGB value Chocolate FXRGB 255 127 36 Chocolate2 FXRGB 238 118 33 Chocolate3 FXRGB 205 102 29 Chocolate4 FXRGB 139 69 19 Coral FXRGB 255 127 80 Corall FXRGB 255 114 86 Coral2 FXRGB 238 106 80 Coral3 FXRGB 205 91 69 Coral4 FXRGB 139 62 47 CornflowerBlue FXRGB 100 149 237 Cornsilk FXRGB 255 248 220 Cornsilk1 FXRGB 255 248 220 Cornsilk2 FXRGB 238 232 205 Cornsilk3 FXRGB 205 200 177 Cornsilk4
23. Figure 3 19 An example of a tree widget You can also specify icons to be used for each tree item The open icon is displayed next to an item when it is selected the closed icon is displayed when the item is not selected These icons are not associated with the expanded collapsed state of a branch For example Microsoft s Windows Explorer uses open and closed folder icons to show the selected state You can check if an item is selected using the tree s isItemSelected method The tree widget will send its target a SEL_ COMMAND message whenever the user clicks on an item You can handle this message and then traverse all the items in the tree to find the selected item The following example uses a message handler that assumes that the tree is browse select and allows the user to select only one item at a time def onCmdTree self sender sel ptr w self tree getFirstItem while w if self tree isItemSelected w Do something here based on the selected item w break if w getFirst w w getFirst continue while not w getNext and w getParent w w getParent w w getNext 3 16 TABLE WIDGET 3 5 2 Option tree list 3 6 The AFXOptionTreeList widget provides a tree structure of children that can be toggled The tree structure includes branches along with leaves at the end of a branch The user can toggle the leaves of the tree on or off The user can also toggle the entire branch on or off The toggle
24. GUI module Creating a GUI toolset This section describes how you can create a GUI toolset Customizing an existing module or toolset The previous sections describe how you can create a new module or toolset Alternatively the ABAQUS GUI Toolkit allows you to derive a new module or toolset from an existing module or toolset and to add or remove functionality from it Creating an application This section explains how to create an application such as ABAQUS CAE It also describes the high level infrastructure that is responsible for running the application The application object This section describes the ABAQUS application object The application object manages the message queue timers chores GUI updating and other system facilities The main window This section describes the layout components and behavior of the ABAQUS main window Customizing the main window The main window base class provides the GUI infrastructure to allow user interaction the manipulation of modules and the display of objects in the viewport This section describes how you add functionality to an application by deriving from the main window base class and then registering modules and toolsets Part Il Getting Started This part describes an application that uses the ABAQUS GUI Toolkit This part also describes how you can use the ABAQUS GUI Toolkit to create plug ins The following topic is covered e Chapter 2 Getting started with the ABAQ
25. PeachPuff4 Peru Pink Pink1 Pink2 Pink3 Pink4 Plum Plum1 Plum2 Plum3 Plum4 PowderBlue Purple Purplel Purple2 Purple3 Purple4 Red FXRGB 255 130 171 FXRGB 238 121 159 FXRGB 205 104 137 FXRGB 139 71 93 FXRGB 255 239 213 FXRGB 255 218 185 FXRGB 255 218 185 FXRGB 238 203 173 FXRGB 205 175 149 FXRGB 139 119 101 FXRGB 205 133 63 FXRGB 255 192 203 FXRGB 255 181 197 FXRGB 238 169 184 FXRGB 205 145 158 FXRGB 139 99 108 FXRGB 221 160 221 FXRGB 255 187 255 FXRGB 238 174 238 FXRGB 205 150 205 FXRGB 139 102 139 FXRGB 176 224 230 FXRGB 160 32 240 FXRGB 155 48 255 FXRGB 145 44 238 FXRGB 125 38 205 FXRGB 85 26 139 FXRGB 255 0 0 B 20 APPENDIX B COLORS AND RGB VALUES String RGB value Red1 FXRGB 255 0 0 Red2 FXRGB 238 0 0 Red3 FXRGB 205 0 0 Red4 FXRGB 139 0 0 RosyBrown FXRGB 188 143 143 RosyBrown1 FXRGB 255 193 193 RosyBrown2 FXRGB 238 180 180 RosyBrown3 FXRGB 205 155 155 RosyBrown4 FXRGB 139 105 105 RoyalBlue FXRGB 65 105 225 RoyalBluel FXRGB 72 118 255 RoyalBlue2 FXRGB 67 110 238 RoyalBlue3 FXRGB 58 95 205 RoyalBlue4 FXRGB 39 64 139 SaddleBrown FXRGB 139 69 19 Salmon FXRGB 250 128 114 Salmonl FXRGB 255 140 105 Salmon2 FXRGB 238 130 98 Salmon3 FXRGB 205 112 84 Salmon4 FXRGB 139 76 57 SandyBrown FXRGB 244 164 96 SeaGreen FXRGB 46 139 87 SeaGreen1 FXRGB 84 255 159 SeaGreen2 FXRGB 78 238 148 Se
26. PlateHeightDB self self step3 AFXDialogStep self self plateHeightDB return self step3 else return None 7 4 5 getLoopStep If you want your procedure to loop you must write the getLoopStep method The getLoopStep method is defined in the base class to return None indicating that the mode will be run through a single time You can redefine the getLoopStep method and return a step to which the procedure should loop back The following example shows how you can make the procedure shown in the previous section loop back to the first step after it has completed the last step def getLoopStep self return self step 7 4 6 AFXDialogStep The AFXDialogStep class allows you to post a dialog box during a procedure To create a dialog step you must supply the procedure a dialog box and optionally a prompt for the prompt line If you do not suppy a prompt ABAQUS uses a default prompt of Fill out the dialog box title dialog The following is an example of a dialog step in a single step procedure def getFirstStep self db PlateDB self prompt Enter plate dimensions in the dialog box return AFXDialogStep self db prompt In most cases a procedure will have more than one step Since a procedure has the ability to back up to previous steps you must write procedures that do not construct dialog boxes more than once during the procedure You can prevent a procedure from constructing dialog boxes more than once by initializi
27. The context bar Section 13 5 e The module toolbox Section 13 6 e The drawing area and canvas Section 13 7 e The prompt area Section 13 8 e The message area Section 13 9 e The command line interface Section 13 10 13 1 An overview of the main window Interactive ABAQUS products consist of a single main window that contains several GUI infrastructure components The main window itself provides only GUI infrastructure support You add specific functionality to the application by registering modules and toolsets with the main window Registering modules and toolsets is discussed in detail in Modules and toolsets Section 14 1 The main window is designed to work with the concept of GUI modules which contain their own menu bar toolbar and toolbox entries The main window shows only the components for one module at atime The main window is responsible for swapping these components in and out as the user visits the various modules of the application The following statement shows the constructor that you use to create the main window AFXMainWindow app title icon None minilcon None opts DECOR_ALL x 0 y 0 w 0 h 0 The following list describes the arguments to the AFXMainWindow constructor app The application object title A String that will be shown in the title bar of the main window THE TITLE BAR icon A 32 x 32 pixel icon used for the application on the desktop minilc
28. Toolkit Reference Manual for a complete listing of widget classes The following topics are covered 3 1 Labels and buttons Section 3 1 Text widgets Section 3 2 Lists and combo boxes Section 3 3 Range widgets Section 3 4 Tree widgets Section 3 5 Table widget Section 3 6 Miscellaneous widgets Section 3 7 The create method Section 3 8 Widgets and fonts Section 3 9 Labels and buttons This section describes the widgets in the ABAQUS GUI Toolkit that use labels and buttons The following topics are covered 3 1 1 An overview of labels and buttons Section 3 1 1 Labels Section 3 1 2 Push buttons Section 3 1 3 Check buttons Section 3 1 4 Radio buttons Section 3 1 5 Menu buttons Section 3 1 6 Popup menus Section 3 1 7 Toolbar and toolbox buttons Section 3 1 8 Flyout buttons Section 3 1 9 Color buttons Section 3 1 10 An overview of labels and buttons Several widgets in the ABAQUS GUI Toolkit support labels If you want to put a label before a text field for example you should use AFXTextField instead of creating a horizontal frame and adding 3 1 LABELS AND BUTTONS a label widget and a text field widget The following sections describe the specific widgets that support labels The label and button constructors all take a text string argument This text string can consist of three parts
29. and message handlers work together class MyClass BaseClass ID_1 ID_2 ID_LAST range BaseClass ID_ LAST BaseClass ID LAST 3 def _ init _ self GUI COMMANDS BaseClass init self FXMAPFUNC self SEL COMMAND self ID_1 MyClass onCmdPrintMsg FXMAPFUNC self SEL COMMAND self ID 2 MyClass onCmdPrintMsg FXButton self Button 1 self self ID 1 FXButton self Button 2 self self ID 2 def onCmdPrintMsg self sender sel ptr if SELID sel self ID 1 print Button 1 was pressed elif SELID sel self ID 2 print Button 2 was pressed return 1 The previous example starts by generating a list of IDs for use in the derived class Since a widget has a specific target the ID of a widget does not have to be globally unique it needs to be unique only within the target s class and base classes To handle this numbering automatically the convention is to define ID_LAST in each class A derived class should begin its numbering using the value of ID LAST defined in its base class In addition a derived class should define its own ID_LAST as the last ID in the derived class A class that derives from the derived class will then be able to make use of that ID to begin its numbering ID_LAST should not be used by any widget The only purpose of ID_LAST is to provide an automatic numbering scheme between classes The example continues by constructing a message map by adding entries using the FXMAPFU
30. be unposted without any processing e If the user clicks Cancel from the standard warning dialog box the data dialog box will remain posted and no action will be taken 5 6 4 Constructor contents You use the constructor of the dialog box to create the widgets that will appear in the dialog box To keep the GUI up to date with the application state and vice versa you use keywords as targets of widgets Keywords are defined as members of a form and the form is passed to the dialog box as a dialog box constructor argument For more information see AF XKeywords Section 6 4 8 The following script shows how you can use keywords to construct a dialog box class GraphicsOptionsDB AFXDataDialog Innnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn def __init_ self form AFXDataDialog init _ self form Graphics Options self OK self APPLY self DEFAULTS self CANCEL Hardware frame gb FXGroupBox self Hardware FRAME GROOVE LAYOUT FILL X hardwareFrame FXHorizontalFrame gb 0 0 0 0 0 0 0 0 0 FXLabel hardwareFrame Driver FXRadioButton hardwareFrame OpenGL form graphicsDriverKw OPEN _ GL getId FXRadioButton hardwareFrame X11 form graphicsDriverKw X11 getId FXCheckButton gb Use double buffering form doubleBufferingKw displayListBtn FXCheckButton gb Use display lists form displayListsKw View Manipulation frame gb FXGroupBox self View Manipulation
31. default values when the user presses the Defaults button in the dialog box You can register a defaults object with a command as follows self registerDefaultsObject cmd session defaultGraphicsOptions In addition the AFXGuiCommand class has a setKeywordValuesToDefault method that you can use to initialize the state of all keywords in a command In most cases you use the setKeywordValuesToDefault method to initialize the state of all keywords in the getFirstDialog method of the mode As a result the application will initialize the value of the keywords in a command each time the dialog box is posted If no defaults object is specified the command uses the default values specified in the keyword s constructor when the user presses the Defaults button in the dialog box RECEIVING NOTIFICATION OF KERNEL DATA CHANGES 6 5 AFXTargets Targets are similar to keywords in that they automatically keep their data synchronized with the GUI however targets do not participate in command processing Targets are typically used to monitor the value of some widget in the GUI that is not directly related to a command for example selecting the type of load to create from the Create Load dialog box The following types of targets are supported e AFXIntTarget initialValue e AFXFloatTarget initialValue e AFXStringTarget initialValue 6 6 Accessing kernel data from the GUI You can use the kernelAccess module to query the GUI side mdb and se
32. e The ability to display the current value above the drag handle For example slider AFXSlider p 0 0 AFXSLIDER_INSIDE_BAR AFXSLIDER_SHOW_VALUE LAYOUT_FILL_X slider setMinLabelText Min slider setMaxLabelText Max slider setDecimalPlaces 1 slider setRange 20 80 slider setValue 50 Min Max 50 Die as Figure 3 17 An example of a slider from AFXSlider 3 4 2 Spinners The AFXSpinner widget combines a text field and two arrow buttons The arrows increment the integer value shown in the text field AFXSpinner extends the capability of the FXSpinner widget by providing an optional label For example spinner AFXSpinner p 4 AFXSpinner spinner setRange 20 80 spinner setValue 50 AFXSpinner 504 Figure 3 18 An example of a spinner from AFXSpinner The AFXFloatSpinner widget is similar to the AFXSpinner widget but it allows floating point values TREE WIDGETS 3 5 Tree widgets This section describes the tree widgets in the ABAQUS GUI Toolkit A tree widget arranges its children in a hierarchical fashion and allows the various branches to be expanded or collapsed A file browser such as Microsoft Windows Explorer is a common example of an application that makes use of a tree widget The following topics are covered e Tree list Section 3 5 1 e Option tree list Section 3 5 2 3 5 1 Tree list The FXTreeList widget provides a tree structure of children that can be expa
33. kernel objects Section 6 7 1 e Manually registering a query on kernel objects Section 6 7 2 e Recognizing when custom kernel data change Section 6 7 3 RECEIVING NOTIFICATION OF KERNEL DATA CHANGES 6 7 1 Automatically registering a query on kernel objects Queries provide a mechanism that allows the GUI process to be notified when data in the kernel change Keeping the GUI and commands up to date Section 6 4 3 describes how you use the registerQuery argument of the AFXGuiCommand constructor The registerOuery argument is a Boolean flag that specifies whether to register a query automatically on the object being edited by the specified kernel command Ifthe kernel object specified in the AFXGuiCommand constructor changes the infrastructure updates the keywords in the GUI with the latest values As a result you do not need to register a query explicitly By default registerQuery FALSE and the query is not automatically registered For example cmd AFXGuiCommand mode setValues mdb models s parts s TRUE In this example ifthe user changes the current part the path to the setValues method is updated to reflect the new current part As a result when the user clicks OK to commit a customized dialog box the mode issues a setValues command that modifies the current part 6 7 2 Manually registering a query on kernel objects For objects not directly related to a command such as a repository you may wish to
34. nz RUSSIA BELARUS amp UKRAINE TESIS Ltd Office 701 703 18 Unnatov Str 127083 Moscow Russia Tel 7 095 212 44 22 Fax 7 095 212 42 62 E mail info tesis com ru SOUTH AFRICA Finite Element Analysis Services Pty Ltd Unit 4 The Waverley Wyecroft Road Mowbray 7700 Tel 27 21 448 7608 Fax 27 21 448 7679 E mail feas feas co za SPAIN Principia Ingenieros Consultores S A Velazquez 94 E 28006 Madrid Tel 34 91 209 1482 Fax 34 91 575 1026 E mail abaqus principia es TAIWAN APIC 11F No 71 Sung Chiang Road Taipei 10428 Tel 886 02 25083066 Fax 886 02 25077185 E mail apic apic com tw TURKEY A Ztech Ltd Perdemsac Plaza Teknoloji Evi Bayar Cad Gulbahar Sok No 17 Kozyatagi 34742 Istanbul TURKIYE Tel 90 216 361 8850 Fax 90 216 361 8851 E mail info a ztech com tr SWEDEN ABAQUS Scandinavia FEM Tech AB Pilgatan 8c SE 72130 V ster s Tel 46 21 12 64 10 Fax 46 21 18 12 44 E mail abaqus abaqus se THAILAND Worley Advanced Analysis 333 Lao Peng Nguan 1 Building 20th Floor Unit B Soi Chaypuang Vibhavadi Rangsit Road Ladyao Jatujak Bangkok 10900 Thailand Tel 66 2 689 3000 Fax 66 2 618 8109 E mail abaqus th worley com au UNITED KINGDOM Cheshire ABAQUS UK Ltd The Genesis Centre Science Park South Birchwood Warrington Cheshire WA3 7BH Tel 44 1 925 810166 Fax 44 1 925 810178 E mail hotline abaqus co uk S
35. register a query yourself You can register a query on an ABAQUS CAE object using the registerQuery method This method takes a callback function as an argument When the object upon which the query is registered changes the infrastructure automatically calls the function supplied in the registerQuery method For example from abaqusGui import from kernelAccess import mdb def onPartsChanged print The parts repository changed keys mdb models Model 1 parts keys print The new keys are keys mdb models Model 1 parts registerQuery onPartsChanged In the previous example if a part is created deleted renamed or edited the onPartsChanged method will be called The registerQuery method takes an optional second argument that determines whether or not the callback is called when the query is first registered By default this argument is TRUE and the callback will be called when the query is first registered If you specify FALSE as the second argument the query callback is not called when the query is first registered 6 20 RECEIVING NOTIFICATION OF KERNEL DATA CHANGES Since registered queries create traffic between the kernel and GUI processes you should unregister queries when you do not need them To unregister a query use the unregisterQuery method and pass the same arguments that you used in the registerQuery method In most cases you register queries within the show method that you write for your
36. setItemColor 2 1 00FFO00 table setItemColor 3 1 0000FF Figure 3 30 Including icons in table cells 3 28 3 6 11 Popup menu TABLE WIDGET You can add a popup menu to the table by specifying the appropriate flags using the setPopupOptions method The menu will be posted when the user clicks mouse button 3 anywhere over the table The following options are supported in the popup menu Option flag Effect POPUP_NONE default No popup menu will be displayed POPUP_CUT Adds a Cut button to the popup menu POPUP_COPY Adds a Copy button to the popup menu POPUP_PASTE Adds a Paste button to the popup menu POPUP_EDIT POPUP_CUT POPUP_COPY POPUP_PASTE POPUP_INSERT ROW POPUP_INSERT COLUMN POPUP_DELETE ROW POPUP_DELETE COLUMN POPUP_CLEAR CONTENTS POPUP_MODIFY Adds Insert Row Before After buttons to the popup menu Adds Insert Column Before After buttons to the popup menu Adds Delete Rows button to the popup menu Adds Delete Columns button to the popup menu Adds Clear Contents Table buttons to the popup menu POPUP_INSERT_ROW POPUP_INSERT_COLUMN POPUP DELETE ROW POPUP DELETE COLUMN POPUP CLEAR CONTENTS POPUP READ FROM FILE POPUP ALL Adds Read from File button to the popup menu POPUP_EDIT POPUP_MODIFY POPUP_READ Figure 3 31 and the following example shows how you can enable various popup menu options vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0
37. setLeadingRowLabels State tLayer table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnType 0 table BOOL table setColumnWidth 0 50 table setColumnJustify 0 AFXTable CENTER from appIcons import lockedData unlockedData trueIcon FXXPMIcon getAFXApp lockedData falseIcon FXXPMIcon getAFXApp unlockedData table setDefaultBoolIcons trueIcon falseIcon Figure 3 28 Defining your own true and false icons 3 6 9 Icon type If you want to display an icon in an item you must set the type of the column to be ICON and assign the icons to be shown This type of column is not editable by the user The following example shows how you can include an icon in a table cell vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 3 26 TABLE WIDGET AFXTABLE NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table setLeadingRowLabels tStatus table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnType 0 table setColumnWidth 0 table ICON 30 table setColumnJustify 0 AFXTable CENTER from appIcons import circleData squareData circleIcon FXXPMIcon getAFXApp circleData squarelcon FXXPMIcon getAFXApp squareData table setItemlIcon 1 table setItemlIcon 2 table setItemlIcon 3 3 6 10 Color type Figure 3 29 circleIcon squarelcon circleIcon Failed Running
38. state In a pull state the widgets are interrogating the application to keep up to date 6 4 6 Data targets In a typical GUI application you will want to do the following 1 Initialize the values in a dialog box 2 Post the dialog box to allow the user to make changes 3 Collect the changes from the dialog box In addition you may want the dialog box to update its state if some application state is updated while the dialog box is posted Data targets are designed to make these tasks easier for the GUI programmer This section describes how the data targets work The following sections describe how the ABAQUS GUI Toolkit has extended this concept to keywords that are used to construct commands sent to the kernel A data target acts as a bi directional intermediary between some application state and GUI widgets More than one widget can be connected to a data target but a data target acts on only one piece of application state When the user uses the GUI to change a value the application state monitored by 6 9 GUI COMMANDS the data target is updated automatically Conversely when the application state is updated the widget connected to the data target is updated automatically As described in Automatic GUI updating Section 6 4 5 widgets can be in a push state or a pull state Push state In a push state the widgets are collecting and sending user input to the application Figure 6 3 illustrates how a data target works wi
39. step AFXPickStep self self edgeKw Select a straight edge EDGES step setEdgeRefinements STRAIGHT By default no refinements are set For a complete list of refinements see the ABAQUS GUI Toolkit Reference Manual 7 5 3 Nonpickable entities By default the procedure mode prevents previously selected geometric entities from being selected twice in the same procedure If you do not want this behavior you can call the allowRepeatedSelections method The following example shows how to allow repeated selections step AFXPickStep self self edgeKw Select a straight edge EDGES step allowRepeatedSelections TRUE Disallowing repeated picks works only for geometry items such as vertices edges and faces it does not work for nodes and elements 7 16 PICKING IN PROCEDURE MODES 7 5 4 Highlighting while selecting The procedure mode clears all highlighting when the user cancels a procedure In addition the procedure mode clears highlighting in the current step before backing up The color of highlighted entities is controlled by the highlight level set in the AFXPickStep constructor 7 5 5 Selection options The Selection Options dialog box is automatically available in any pick step The available options in the Selection Options dialog box are automatically configured based on the types of entities that the user is picking For example if the user is picking only faces only Faces appears in the combo box in the dia
40. the dialog box processing yourself The AFXDialog class extends the FXDialog class by providing the following features e Button flags that allow the automatic construction of action area buttons CUSTOM DIALOG BOXES e Option flags that control the placement of the action area Option flags also determine whether to include a separator between the action area and the rest of the dialog box e Message IDs for the various action area commit semantics e Methods to add action area buttons manually e Automatic handling of the No Cancel and Dismiss buttons Automatic handling is also provided for the Close X button on the right hand side of the dialog box s title bar e Automatic destruction of the dialog box after it is unposted See Action area Section 5 5 4 for more details 5 5 2 Constructors There are three prototypes of the AFXDialog constructor The difference between the three prototypes is the occluding behavior of the dialog box as illustrated in the following examples e The following statement creates a dialog box that always occludes the main window when overlapping with the main window AFXDialog title actionButtonIds 0 opts DIALOG NORMAL x 0 y 0 w 0 h 0 e The following statement creates a dialog box that always occludes its owner widget usually a dialog box when overlapping with the widget AFXDialog owner title actionButtonIds 0 opts DIALOG NORMAL x 0 y 0 w 0 h 0 e The
41. to the value of its data 13 and sends an uncheck message back to the radio button since the values do not match 3 The second radio button then sends a 13 SEL_UPDATE message to the data target 4 The data target compares the values and sends a check message back to the radio button since the values do match 5 Similarly the third button receives an uncheck message from the data target since the values of the message ID and its data do not match In this way the ABAQUS GUI Toolkit automatically maintains the radio button behavior only one button at a time will ever be checked GUI COMMANDS ID1 SEL_UPDATE Option 1 ID 2 ID_UNCHECK SEL_COMMAND The data ID2 SEL_UPDATE Option2 a Data Target data target ID_CHECK SEL_COMMAND updates ID 13 the three radio buttons ID3 SEL_UPDATE O Option3 ID 58 ID_UNCHECK SEL_COMMAND Figure 6 5 A data target operating on three radio buttons in option mode and a pull state 6 4 8 AFXKeywords Keywords generate the arguments to a GUI command These keywords belong to the command but the keywords are also stored as members of the mode As a result you can easily connect the keywords to widgets in a dialog box that updates the value of the keywords For more information see Chapter 5 Dialog boxes AFXKeyword is the base class for keywords in the toolkit The AFXKeyword class derives from a data target so it automatically keeps the GU
42. you must define itas c None s None not just c None blueIconData 12 12 2 1 c None s None m c blue blueIcon FXXPMIcon getAFXApp blueIconData Figure A 1 shows the blue square icon created by this example Figure A 1 The blue square icon APPENDIX A ICONS If you construct an icon after creating the widget in which the icon will be used you must call the icon s create method before using it in the widget For more information see The create method Section 3 8 APPENDIX B COLORS AND RGB VALUES Appendix B Colors and RGB values When you are specifying a color some methods require a string and other methods require an FXColor To create an FXColor you use the FXRGB function and pass in the appropriate values for red green and blue The following table shows a list of valid color strings and the corresponding RGB values String RGB value AliceBlue FXRGB 240 248 255 Antique White FXRGB 250 235 215 AntiqueWhitel FXRGB 255 239 219 AntiqueWhite2 FXRGB 238 223 204 AntiqueWhite3 FXRGB 205 192 176 AntiqueWhite4 FXRGB 139 131 120 Aquamarine FXRGB 127 255 212 Aquamarinelq FXRGB 127 255 212 Aquamarine2 FXRGB 118 238 198 Aquamarine3 FXRGB 102 205 170 Aquamarine4 FXRGB 69 139 116 Azure FXRGB 240 255 255 Azurel FXRGB 240 255 255 Azure2 FXRGB 224 238 238 Azure3 FXRGB 193 205 205 Azure4 FXRGB 131 139 139 Beige FXRGB 245 245 220 Bisque FXRGB 255 228 196 Bisquel
43. 0 table AFXTable vf 4 3 4 3 None 0 AFXTABLE NORMAL AFXTABLE EDITABLE table setLeadingColumns 1 table setLeadingRows 1 table setLeadingRowLabels X tY table showHorizontalGrid TRUE table showVerticalGrid TRUE 3 29 TABLE WIDGET table setColumnWidth 0 30 Center all columns table setColumnJustify 1 table CENTER table setPopupOptions AFXTable POPUP_CUT AFXTable POPUP_COPY AFXTable POPUP_PASTE AFXTable POPUP_INSERT_ROW AFXTable POPUP_DELETE ROW AFXTable POPUP_CLEAR_CONTENTS AFXTable POPUP_READ FROM FILE 3 6 12 Colors Items in a table that display characters have two sets of colors the normal color and the selected color In addition each item has a background color and a text color To change these colors the table widget provides the following controls e Item text color e Item background color e Selected item text color e Selected item background color e Item color color button The color button is described in Color buttons Section 3 1 10 You can control the text color of items that display characters using the setItemTextColor method Items that display characters include strings numbers and lists You can control the text color of these items when they are selected by using the setSelTextColor method You can control the background color of any item by using the setItemBackColor method You can control the background color of any item when it is selecte
44. 0 Grey51 Grey52 Grey53 Grey54 Grey55 Grey56 Grey57 Grey58 Grey59 Grey6 Grey60 Grey61 Grey62 Grey63 Grey64 Grey65 Grey66 Grey67 Grey68 Grey69 Grey7 Grey70 Grey71 Grey72 FXRGB 122 122 122 FXRGB 125 125 125 FXRGB 13 13 13 FXRGB 127 127 127 FXRGB 130 130 130 FXRGB 133 133 133 FXRGB 135 135 135 FXRGB 138 138 138 FXRGB 140 140 140 FXRGB 143 143 143 FXRGB 145 145 145 FXRGB 148 148 148 FXRGB 150 150 150 FXRGB 15 15 15 FXRGB 153 153 153 FXRGB 156 156 156 FXRGB 158 158 158 FXRGB 161 161 161 FXRGB 163 163 163 FXRGB 166 166 166 FXRGB 168 168 168 FXRGB 171 171 171 FXRGB 173 173 173 FXRGB 176 176 176 FXRGB 18 18 18 FXRGB 179 179 179 FXRGB 181 181 181 FXRGB 184 184 184 APPENDIX B COLORS AND RGB VALUES String RGB value Grey73 FXRGB 186 186 186 Grey74 FXRGB 189 189 189 Grey75 FXRGB 191 191 191 Grey76 FXRGB 194 194 194 Grey77 FXRGB 196 196 196 Grey78 FXRGB 199 199 199 Grey79 FXRGB 201 201 201 Grey8 FXRGB 20 20 20 Grey80 FXRGB 204 204 204 Grey81 FXRGB 207 207 207 Grey82 FXRGB 209 209 209 Grey83 FXRGB 212 212 212 Grey84 FXRGB 214 214 214 Grey85 FXRGB 217 217 217 Grey86 FXRGB 219 219 219 Grey87 FXRGB 222 222 222 Grey88 FXRGB 224 224 224 Grey89 FXRGB 227 227 227 Grey9 FXRGB 23 23 23 Grey90 FXRGB 229 229 229 Grey91 FXRGB 232 232 232 Grey92 FXRGB 235 235 235 Grey93 FXRGB 237 237 237 Grey94 FXRGB 240 240 240 G
45. 1194 E mail support AbaqusWest com AUSTRALIA Worley Advanced Analysis Level 17 300 Flinders Street Melbourne Vic 3000 Tel 61 3 8612 5132 Fax 61 3 9205 0573 E mail abaqus worley com au AUSTRIA ABAQUS Austria GmbH Zinckgasse 20 22 2 13 A 1150 Vienna Austria Tel 43 1 929 16 25 0 Fax 43 1 929 16 25 20 E mail support abaqus at CHINA ABAQUS China Room A 2703 Eagle Plaza No 26 Xiao Yun Rd Beijing 100016 P R China Tel 86 01 84580366 Fax 86 01 84580360 E mail abaqus abaqus com cn FRANCE ABAQUS France SAS 7 rue Jean Mermoz Bat A 78000 Versailles Tel 33 01 39 24 15 40 Fax 33 01 39 24 15 45 E mail support abaqus fr GERMANY Munich ABAQUS Deutschland GmbH Sendlinger Tor Platz 8 D 80336 Miinchen Tel 49 89 5999 1768 Fax 49 89 5999 1767 E mail info abaqus de ITALY ABAQUS Italia s r l Via Domodossola 17 20145 Milano MI Tel 39 02 39211211 Fax 39 02 31800064 E mail info abaqus it BENELUX ABAQUS Benelux BV Huizermaatweg 576 1276 LN Huizen The Netherlands Tel 31 35 52 58 424 Fax 31 35 52 44 257 E mail support abaqus nl CZECH REPUBLIC Synerma s r 0 Huntirov 58 468 22 Skuhrov Czech Republic Tel 420 603 145 769 Fax 420 603 181 944 E mail abaqus synerma cz GERMANY Aachen ABAQUS Deutschland GmbH Theaterstra e 30 32 D 52062 Aachen Tel 49 241 474010 Fax 49 241 4090963 E mail info abaqus de INDIA Chenna
46. 54 73 Tan3 FXRGB 205 133 63 Tan4 FXRGB 139 90 43 Thistle FXRGB 216 191 216 Thistle FXRGB 255 225 255 Thistle2 FXRGB 238 210 238 Thistle3 FXRGB 205 181 205 Thistle4 FXRGB 139 123 139 Tomato FXRGB 255 99 71 Tomatol FXRGB 255 99 71 Tomato2 FXRGB 238 92 66 Tomato3 FXRGB 205 79 57 Tomato4 FXRGB 139 54 38 Turquoise FXRGB 64 224 208 Turquoisel FXRGB 0 245 255 B 23 APPENDIX B COLORS AND RGB VALUES String RGB value Turquoise2 FXRGB 0 229 238 Turquoise3 FXRGB 0 197 205 Turquoise4 FXRGB 0 134 139 Violet FXRGB 238 130 238 VioletRed FXRGB 208 32 144 VioletRed1 FXRGB 255 62 150 VioletRed2 FXRGB 238 58 140 VioletRed3 FXRGB 205 50 120 VioletRed4 FXRGB 139 34 82 Wheat FXRGB 245 222 179 Wheat 1 FXRGB 255 231 186 Wheat2 FXRGB 238 216 174 Wheat3 FXRGB 205 186 150 Wheat4 FXRGB 139 126 102 White FXRGB 255 255 255 WhiteSmoke FXRGB 245 245 245 Yellow FXRGB 255 255 0 Yellowl FXRGB 255 255 0 Yellow2 FXRGB 238 238 0 Yellow3 FXRGB 205 205 0 Yellow4 FXRGB 139 139 0 YellowGreen FXRGB 154 205 50 B 24
47. A CHANGES e RegisteredDictionary allows you to create custom dictionaries For more information see Registered dictionaries Section 5 6 7 of the ABAQUS Scripting User s Manual e RegisteredList allows you to create custom lists For more information see Registered lists Section 5 6 8 of the ABAQUS Scripting User s Manual e RegisteredTuple allows you to create custom tuples For more information see Registered tuples Section 5 6 9 of the ABAQUS Scripting User s Manual For more information on the customKernel module see Extending the ABAQUS Scripting Interface Section 5 6 of the ABAQUS Scripting User s Manual 6 22 MODE PROCESSING 7 Modes A mode is a mechanism for gathering input from the user processing that input and then issuing a command to the kernel This section describes the modes that are available in the ABAQUS GUI Toolkit The following topics are covered e An overview of modes Section 7 1 e Mode processing Section 7 2 e Form modes Section 7 3 e Procedure modes Section 7 4 e Picking in procedure modes Section 7 5 7 1 An overview of modes There are two types of modes Form Modes Form modes provide an interface to standalone dialog boxes Procedure Modes Procedure modes provide an interface that uses the prompt area to guide the user through a sequence of steps that collect input from dialog boxes or from selections in the viewport
48. AQUS GUI Toolkit looks similar on all platforms This is due to the architecture of the toolkit While the application programming interface API is the same on all platforms the underlying calls made to the operating system s GUI libraries differ on UNIX systems calls are made to the Xt library whereas on Windows systems calls are made to the Win32 library These differences are hidden from the application developer Since the FOX GUI Toolkit is object oriented it allows developers to extend its functionality easily by deriving new classes from the base toolkit The ABAQUS GUI Toolkit takes advantage of this feature by adding special functionality required for ABAQUS GUIs Class names that begin with FX are part of the standard FOX library for example FXButton Class names that begin with AFX are part of the ABAQUS extensions to the FOX library for example AFXDialog When the same class exists with both the FX and AFX prefix for example FXTable and AFXTable you should use the AFX version since it provides enhanced functionality for building applications using ABAQUS 1 4 Organization of the ABAQUS GUI Toolkit User s Manual This manual is organized by functionality and is designed to guide developers through the process of writing an application by explaining how to use the components of the toolkit and by providing snippets of example code A separate ABAQUS GUI Toolkit Reference Manual that contains an alphabetical listing of all of th
49. BAQUS Technical engineering and systems support are provided through the nearest local support office You can contact our offices by telephone fax electronic mail the ABAQUS web based support system or regular mail Information on how to contact each office is listed in the front of each ABAQUS manual The ABAQUS Online Support System AOSS is accessible through the MY ABAQUS section of the ABAQUS Home Page www abaqus com When contacting your local support office please specify whether you would like technical engineering support you have encountered problems performing an ABAQUS analysis or creating a model in ABAQUS or systems support ABAQUS will not install correctly licensing does not work correctly or other hardware related issues have arisen The ABAQUS Online Support System has a knowledge database of ABAQUS Answers The ABAQUS Answers are solutions to questions that we have had to answer or guidelines on how to use ABAQUS We welcome any suggestions for improvements to the support program or documentation We will ensure that any enhancement requests you make are considered for future releases If you wish to file a complaint about the service or products provided by ABAQUS refer to the ABAQUS Home Page Technical engineering support ABAQUS technical support engineers can assist in clarifying ABAQUS features and checking errors by giving both general information on using ABAQUS and information on its application to specific an
50. BAQUS CAE includes detailed descriptions of how to use ABAQUS CAE for model generation analysis and results evaluation and visualization ABAQUS Viewer users should refer to the information on the Visualization module in this manual Analysis e ABAQUS Analysis User s Manual This volume contains a complete description of the elements material models procedures input specifications etc It is the basic reference document for ABAQUS Standard and ABAQUS Explicit Both input file usage and ABAQUS CAE usage information are provided in this manual Examples e ABAQUS Example Problems Manual This volume contains more than 125 detailed examples designed to illustrate the approaches and decisions needed to perform meaningful linear and nonlinear analysis Typical cases are large motion of an elastic plastic pipe hitting a rigid wall inelastic buckling collapse of a thin walled elbow explosive loading of an elastic viscoplastic thin ring consolidation under a footing buckling of a composite shell with a hole and deep drawing of a metal sheet It is generally useful to look for relevant examples in this manual and to review them when embarking on a new class of problem e ABAQUS Benchmarks Manual This online only volume contains over 250 benchmark problems and standard analyses used to evaluate the performance of ABAQUS the tests are multiple element tests of simple geometries or simplified versions of real problems The NAFEMS benchmark prob
51. FXRGB 255 255 255 Gray11 FXRGB 28 28 28 Gray12 FXRGB 31 31 31 Gray13 FXRGB 33 33 33 Gray14 FXRGB 36 36 36 Gray15 FXRGB 38 38 38 Gray16 FXRGB 41 41 41 Gray17 FXRGB 43 43 43 Gray18 FXRGB 46 46 46 B 6 APPENDIX B COLORS AND RGB VALUES String RGB value Gray 19 FXRGB 48 48 48 Gray2 FXRGB 5 5 5 Gray20 FXRGB 51 51 51 Gray21 FXRGB 54 54 54 Gray22 FXRGB 56 56 56 Gray23 FXRGB 59 59 59 Gray24 FXRGB 61 61 61 Gray25 FXRGB 64 64 64 Gray26 FXRGB 66 66 66 Gray27 FXRGB 69 69 69 Gray28 FXRGB 71 71 71 Gray29 FXRGB 74 74 74 Gray3 FXRGB 8 8 8 Gray30 FXRGB 77 77 77 Gray31 FXRGB 79 79 79 Gray32 FXRGB 82 82 82 Gray33 FXRGB 84 84 84 Gray34 FXRGB 87 87 87 Gray35 FXRGB 89 89 89 Gray36 FXRGB 92 92 92 Gray37 FXRGB 94 94 94 Gray38 FXRGB 97 97 97 Gray39 FXRGB 99 99 99 Gray4 FXRGB 10 10 10 Gray40 FXRGB 102 102 102 Gray41 FXRGB 105 105 105 Gray42 FXRGB 107 107 107 Gray43 FXRGB 110 110 110 APPENDIX B COLORS AND RGB VALUES String RGB value Gray44 Gray45 Gray46 Gray47 Gray48 Gray49 Gray5 Gray50 Gray51 Gray52 Gray53 Gray54 Gray55 Gray56 Gray57 Gray58 Gray59 Gray6 Gray60 Gray61 Gray62 Gray63 Gray64 Gray65 Gray66 Gray67 Gray68 Gray69 FXRGB 112 112 112 FXRGB 115 115 115 FXRGB 117 117 117 FXRGB 120 120 120 FXRGB 122 122 122 FXRGB 125 125 125 FXRGB 13 13
52. I and application data synchronized with each other For more information see Data targets Section 6 4 6 The AFXKeyword class extends the functionality of the FXDataTarget class by holding additional values such as the name of the keyword a default value and a previous value The keyword s GUI command uses this information to construct a kernel command string You can designate a keyword as optional or required A required keyword is always issued by the GUI command An optional keyword whose values have not changed since the last commit of the command is not issued by the GUI command Ifnone of the keywords has changed since the last commit no GUI command will be issued when the mode is committed The following types of keywords are supported AFXIntKeyword cmd name isRequired defaultValue AFXFloatKeyword cmd name isRequired defaultValue 6 12 GUI COMMANDS AFXStringKeyword cmd name isRequired defaultValue AFXBoolKeyword cmd name booleanType isRequired defaultValue AFXSymConstKeyword cmd name isRequired defaultValue AFXTupleKeyword cmd name isRequired minLength maxLength opts AFXTableKeyword cmd name isRequired minLength maxLength opts AFXObjectKeyword cmd name isRequired defaultValue The type of data supported by each keyword is implied from the name of its constructor except for AFXObjectKeyword An object keyword is one that supports specifying a variable name as the key
53. ID GUI Infrastructure zu Modules Toolsets A j Menus Icons CETINE x Modes Model Configuration I m Forms Procedures Geometric Properts ee fin Dialogs Prompt line dialogs viewport o_o Material tow Type Force C Prevare Layout Managers Al Mapas rarw 1 Widgets Figure 2 1 An overview of an ABAQUS GUI application be used by one or more GUI modules The Datum tools in ABAQUS CAE are an example of a GUI toolset RUNNING THE PROTOTYPE APPLICATION The application The application is responsible for high level activities such as managing the GUI process used by the application and updating the state of the widgets In addition the application is responsible for interacting with the desktop s window manager 2 2 Plug ins and customized applications There are two ways you can make use of the ABAQUS GUI Toolkit through the use of the plug in architecture or by creating a custom application Plug ins Plug ins are available from the Plug ins menu in the ABAQUS CAE main menu bar ABAQUS plug ins execute ABAQUS Scripting Interface and ABAQUS GUI Toolkit commands and they provide a way to customize ABAQUS CAE for your particular needs or preferences For example a simple plug in could automatically print the contents of the current viewport according to some predefined options The plug in architecture is built into ABAQUS CAE As a result you can customize ABAQUS CAE without creating an application a main window or ev
54. LIGNMENT FOR COMPOSITE CHILDREN In general you should accept the default values for spacing Some compound widgets such as AFXTextField AFXComboBox and AFXSpinner have two padding values one for the padding of the internal text field widget and a second for the entire widget that includes a label You set the padding for the internal text field widget by passing padding values into the widget constructor You set the padding for the entire widget by calling one of the padding methods on the widget for example setPadLeft 4 3 Horizontal and vertical frames The FXHorizontalFrame and FXVerticalFrame widgets arrange their children in rows or columns respectively For example vf FXVerticalFrame parent FXButton vf Button 1 FXButton vf Button 2 FXButton vf Button 3 Button 1 Button 2 Button 3 Figure 4 1 An example of a vertical frame from FXVerticalFrame 4 4 Vertical alignment for composite children The AFXVerticalAligner widget is designed to align children that contain multiple children AFXVerticalAligner does the following 1 Finds the maximum width of the first child of each of its children 2 Sets the width of all the first children to the maximum width For example va AFXVerticalAligner parent AFXTextField va 16 Name AFXTextField va 16 Address AFXTextField va 16 Phone Number 4 3 GENERAL PURPOSE LAYOUT MANAGERS 4 5 Name f Address f Phone Numbe
55. Menufitle MenuTitle MenuTitle a MenuCommand MenuCommand MenuCommand MenuCascade gt Menu Bar MenuCommand N P MenuCommand Menu Pane Figure 3 6 The components of a menu The following example illustrates the use of cascading menus menu AFXMenuPane self AFXMenuTitle self amp Menul None menu AFXMenuCommand self menu amp Item 1 None forml AFXMode ID_ACTIVATE subMenu AFXMenuPane self AFXMenuCascade self menu amp Submenu None subMenu AFXMenuCommand self subMenu amp Subitem 1 None form2 AFXMode ID_ACTIVATE Menul Item 1 LCE te te Figure 3 7 An example of cascading menu buttons from AFXMenuCascade LABELS AND BUTTONS In addition to specifying a mnemonic using the amp syntax described in Labels and buttons Section 3 1 you can specify an accelerator in the menu item s label You specify an accelerator by separating it from the button s text by a t For example AFXMenuCommand self menu Graphics Options tCtrl G None GraphicsOptionsForm self AFXMode ID_ACTIVATE 3 1 7 Popup menus You can create a popup menu that appears when the user clicks mouse button 3 over a widget For example the following statements illustrate how you can create a popup menu that contains two buttons that appear when the user clicks mouse button 3 over a tree widget In the dialog box constructor def _ i
56. NC function In this example when a message of type SEL_COMMAND and an ID of ID_1 or ID _2 is received the script calls the onCmdPrintMsg method The two button widgets have their target set to self MyClass However when each widget sends a message the widget sends a different message ID and the message handler checks the ID to determine who sent the message For example if the user clicks the first button the button sends a ID_1 SEL_COMMAND message to MyClass The class s message map routes that message to the onCmdPrintMsg method The onCmdPrintMsg method checks the ID of the incoming message and prints Button 1 was pressed It is important that your message handlers return the proper value to ensure that the GUI is kept up to date Returning a 1 in a message handler tells the toolkit that the message was handled In turn if a message is handled the toolkit assumes that something may have changed that requires an update and the toolkit initiates a GUI update process Returning a 0 in a message handler tells the toolkit that the message was not handled therefore the toolkit does not initiate a GUI update process Messages are normally sent by the GUI infrastructure as the result of some interaction in the GUI However you can send a message directly to an object by calling its handle method The handle method takes three arguments sender selector and userData The sender is generally the object that is GUI COMMANDS sending the m
57. NNING THE PROTOTYPE APPLICATION access to a community of users that fosters the advance of the ABAQUS Scripting Interface and the ABAQUS GUI Toolkit The prototype application is available from the GUI Examples section of the Downloads area Unzip the files and go to the directory containing the files that you downloaded To use the prototype application open the file testDB py in a text editor From the system prompt enter the following abaqus cae custom prototypeApp noStartup The custom parameter indicates that you are executing an application that is a customized version of ABAQUS CAE The noStartup parameter indicates that you want to start ABAQUS CAE without displaying the startup screen For more information see Execution procedure for ABAQUS CAE Section 3 2 3 of the ABAQUS Analysis User s Manual The application creates two icons in the toolbox as shown in Figure 2 2 KTABAQUS CAE Version 6 5 C Eile Model Viewport View t Demo eagl Module U Test Dial x String Integer Float OK Cancel Figure 2 2 The prototype application The F icon reloads the form code testForm py the D icon reloads the dialog box code testDB py If you make changes to the form code click on the F icon to reload that file If you make changes to the dialog box code click on the D icon to reload that file You do not need to exit and restart ABAQUS CAE to see your changes in the form or
58. RGB 154 192 205 LightBlue4 FXRGB 104 131 139 LightCoral FXRGB 240 128 128 LightCyan FXRGB 224 255 255 LightCyan1 FXRGB 224 255 255 LightCyan2 FXRGB 209 238 238 LightCyan3 FXRGB 180 205 205 LightCyan4 FXRGB 122 139 139 LightGoldenrod FXRGB 238 221 130 LightGoldenrod1 FXRGB 255 236 139 LightGoldenrod2 FXRGB 238 220 130 LightGoldenrod3 FXRGB 205 190 112 LightGoldenrod4 FXRGB 139 129 76 LightGolden FXRGB 250 250 210 rodYellow APPENDIX B COLORS AND RGB VALUES String RGB value LightGray LightGreen LightGrey LightPink LightPink1 LightPink2 LightPink3 LightPink4 LightSalmon LightSalmon1 LightSalmon2 LightSalmon3 LightSalmon4 LightSeaGreen LightSkyBlue LightSkyBlue1 LightSkyBlue2 LightSkyBlue3 LightSkyBlue4 LightSlateBlue LightSlateGray LightSlateGrey LightSteelBlue LightSteelBlue1 LightSteelBlue2 LightSteelBlue3 LightSteelBlue4 LightYellow FXRGB 211 211 211 FXRGB 144 238 144 FXRGB 211 211 211 FXRGB 255 182 193 FXRGB 255 174 185 FXRGB 238 162 173 FXRGB 205 140 149 FXRGB 139 95 101 FXRGB 255 160 122 FXRGB 255 160 122 FXRGB 238 149 114 FXRGB 205 129 98 FXRGB 139 87 66 FXRGB 32 178 170 FXRGB 135 206 250 FXRGB 176 226 255 FXRGB 164 211 238 FXRGB 141 182 205 FXRGB 96 123 139 FXRGB 132 112 255 FXRGB 119 136 153 FXRGB 119 136 153 FXRGB 176 196 222 FXRGB 202 225 255 FXRGB 188 210 238 FXRGB 162 181 205 FXRGB 110 123 139 FXRGB 255 255 224
59. RT_ASCENDING values reverse items for value index in values name self sortTable getItemValue index 0 xValue self sortTable getItemValue index 1 yValue self sortTable getItemValue index 2 items append name xValue yValue row 1 for name xValue yValue in items self sortTable setItemValue row 0 name self sortTable setItemValue row 1 xValue self sortTable setItemValue row 2 yValue row 1 YData 3 YData 2 YData 1 Figure 3 33 Sorting table items 3 7 Miscellaneous widgets This section describes a set of miscellaneous widgets in the ABAQUS GUI Toolkit that you can use in your applications The following topics are covered e Separators Section 3 7 1 e Notes and warnings Section 3 7 2 e Progress bar Section 3 7 3 3 33 MISCELLANEOUS WIDGETS 3 7 1 Separators The FXHorizontalSeparator widget and the FXVerticalSeparator widget provide a visual separator to allow separating elements in a GUI The ABAQUS GUI Toolkit also includes a FXMenuSeparator widget that you can use to separate items in a menu pane For example FXLabel parent This is a label above an FXHorizontalSeparator FXHorizontalSeparator parent FXLabel parent This is a label below an FXHorizontalSeparator This is a label above an FXHorizontalseparator This is a label below an FXHorizontalSeparator Figure 3 34 An example of a horizontal separator from FXHorizontal
60. Separator 3 7 2 Notes and warnings The AFXNote widget provides a convenient way to display notes or warnings in a dialog box AFXNote displays either the word Note or the word Warning in a bold font AFXNote also aligns messages that contain more than one line For example AFXNote parent This is an AFXNote information note nthat wraps on two lines AFXNote parent This is an AFXNote warning note NOTE WARNING Note This is an AF XNote information note that wraps on two lines Warning This is an AFXNote warning note Figure 3 35 An example of a note and a warning from AFXNote 3 7 3 Progress bar The AFXProgressBar widget provides feedback during a process that takes a long time to complete You can use several different modes with a progress bar For example 3 34 WIDGETS AND FONTS pb AFXProgressBar parent keyword tgt LAYOUT_FIX_HEIGHT LAYOUT_FIX_WIDTH FRAME SUNKEN FRAME THICK AFXPROGRES SBAR_SCANNER 0 0 200 25 pb setTotal 100 pb setProgress 50 3 8 The create method Most widgets in the ABAQUS GUI Toolkit employ a two stage creation process In the first stage the widget constructor builds the data structures for the widget In the second stage the toolkit calls the widget s create method The create method constructs all the windows required by the widget so that the widget can be displayed on the screen In most cases the application startup script first calls the constru
61. TS 4 12 Tips for specifying layout hints e Do not over specify layout hints In many cases the default values are what you want and you do not need to specify the hints e Think in terms of simple rows and columns and use horizontal or vertical frames whenever possible e To avoid building up excessive padding set the padding to zero in nested layout managers 4 13 MODAL VERSUS MODELESS Dialog boxes This section describes the dialog boxes that you can create using the ABAQUS GUI Toolkit The following topics are covered e An overview of dialog boxes Section 5 1 e Modal versus modeless Section 5 2 e Showing and hiding dialog boxes Section 5 3 e Message dialog boxes Section 5 4 e Custom dialog boxes Section 5 5 e Data dialog boxes Section 5 6 e Common dialog boxes Section 5 7 An overview of dialog boxes The following general types of dialog boxes are available in the ABAQUS GUI Toolkit Message dialog boxes Message dialog boxes allow you to post error warning or informational messages Custom dialog boxes Custom dialog boxes allow you to build any custom interface However you must supply the infrastructure needed to make the dialog box behave as required Data dialog boxes Data dialog boxes provide support for dialog boxes in which users enter data Data dialog boxes are designed to supply user inputs to forms which automatically issue commands For mo
62. This will ensure that you do not override any existing settings in the PYTHONPATH definition To keep the path to your application portable and generic you should use an environment variable to specify the root of the path For a standard ABAQUS installation the ABA_HOME environment variable refers to the same directory as abaqus_dir As a result you can use the ABA_HOME environment variable to specify the directory that contains your customization script for example ABA_HOME customApps myApp For example to include the myApp directory shown above in the PYTHONPATH you should change the PYTHONPATH definition in abaqus aev from this PYTHONPATH ABA_HOME cae Python Lib ABA_HOME cae Python Obj ABA_HOME cae exec lbr PYTHONPATH to this PYTHONPATH ABA_HOME cae Python Lib ABA_HOME cae Python Obj ABA_HOME cae exec lbr ABA_HOME customApps myApp SPYTHONPATH 11 4 INSTALLATION e There are syntax differences between UNIX systems and Windows systems By default ABAQUS uses UNIX syntax and automatically converts the UNIX syntax to Windows syntax if the application is run on a Windows platform However if you need to specify the drive letter of your path on a Windows system you must use Windows syntax To use Windows syntax you must make the following changes to the entire PYTHONPATH line UNIX Windows NAME NAME The following example shows an abaqus aev file that refers to a drive lett
63. UE FALSE showVerticalGrid TRUE FALSE By default the height of the rows is determined by the font being used for the table The default width of a column is 100 pixels You can override these values using the following table methods setRowHeight row height Height is in pixels 3 20 3 6 3 TABLE WIDGET setColumnWidth column width Width is in pixels The following example illustrates the use of some of these methods vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 3 4 3 table setLeadingColumns 1 table setLeadingRows 1 table setLeadingRowLabels X tY table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnWidth 0 30 x Y Figure 3 23 Leading rows and columns Spanning You can make an item in a header row or column span more than one row or column as shown in the following example vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 3 4 3 table setLeadingColumns 1 table setLeadingRows 2 Corner item table setItemSpan 0 0 2 1 3 21 TABLE WIDGET Span top row item over 2 columns table setItemSpan 0 1 1 2 table setLeadingRowLabels Coordinates table setLeadingRowLabels X tY 1 table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnWidth 0 30 Coordinates Figure 3 24 An example of spanning two he
64. US GUI Toolkit 2 2 1 WHAT ARE THE COMPONENTS OF AN ABAQUS GUI APPLICATION Getting started with the ABAQUS GUI Toolkit This chapter provides an overview of a customized GUI application The following topics are covered e What are the components of an ABAQUS GUI application Section 2 1 e Plug ins and customized applications Section 2 2 e Running the prototype application Section 2 3 What are the components of an ABAQUS GUI application There are many components involved in creating a GUI application Figure 2 1 shows an overview of these components and how they are connected This section provides a brief overview of each component The components are discussed in more detail in subsequent chapters Widgets At the lowest level of an application you use widgets to collect input from the user through a graphical user interface For example a text field widget presents a box into which the user can type numbers Similarly a check button widget presents a small box that the user can click on to toggle an option on or off Layout managers Layout managers arrange widgets by providing alignment options For example a horizontal frame arranges widgets in arow A vertical frame arranges widgets in a column Dialog boxes Dialog boxes group widgets inside layout managers and present all the inputs required for a particular function For example the Print dialog box presents all the controls that allow the u
65. Version 6 4 1 If you do not specify the major minor and update numbers in the application constructor they default to the current ABAQUS CAE version numbers If you set the prerelease argument in the AFXApp 13 2 THE TITLE BAR Title bar SS Title string Menu bar Persistent toolset menus Toolbar Persistent toolset tools Module tools Help Info Context bar Module control Context controls Canvas and drawing area Prompt area Message area _ Command line interface Figure 13 1 The main window constructor to TRUE the update number is preceded by PRE For example ABAQUS CAE Version 6 4 PRE1 In addition if the user has opened a model database the title bar string contains the name of the current model database for example ABAQUS CAE Version 6 4 1 MDB C projects cars engines turbo 1 cae If the name of the current model database including the path exceeds 50 characters the name will be abbreviated by showing only the first and last 25 characters separated by If you do not want the default title processing you can override it by specifying a title in the AFXMainWindow constructor If you specify a title in the AFXMainWindow constructor the ABAQUS GUI Toolkit ignores the arguments in the application constructor and uses the title specified The model database name and the name of the current viewport when maximized will continue to be shown in the title bar even if you override the default title proces
66. XCheckButton 6 14 GUI COMMANDS Keyword ID Description AFXSymConstKeyword 0 Keyword operates in value mode Use this value when the keyword is connected to a list or combo box gt 0 Keyword operates in option mode Use the value of the Symbolic Constant s ID when the keyword is connected to a radio button Do not use this keyword with FXCheckButton AFXTupleKeyword 0 Keyword operates in value mode Use this value when the entire tuple is gathered from a single widget 1 Keyword operates in value mode for only the mth 2 element of the tuple where n ID Use this value when 3 the input for each element is gathered from separate widgets AFXTableKeyword 0 Keyword operates in value mode AFXObjectKeyword 0 Keyword operates in value mode 6 4 10 Boolean integer float and string keyword examples The following statements illustrate the use of Boolean integer float and string keywords Boolean keyword FXCheckButton self Show node labels mode nodeLabelsKw 0 Integer keyword AFXTextField self 8 Number of CPUs mode cpusKw 0 Float keyword AFXTextField self 8 Radius mode radiusKw 0 String keyword AFXTextField self 8 Name mode nameKw 0 6 15 GUI COMMANDS 6 4 11 Symbolic constant keyword examples Symbolic constants provide a way to specify choices for a command argument that make the command more readable For example there are
67. XTable constructor is defined by the following prototype AFXTable p numVisRows numVisColumns numRows numColumns tgt None sel 0 opts AFXTABLE NORMAL x 0 y 0 w 0 h 0 pl DEFAULT _MARGIN pr DEFAULT_MARGIN pt DEFAULT MARGIN pb DEFAULT_MARGIN The AFXTable constructor has the following arguments parent The first argument in the constructor is the parent An AFXTable does not draw a frame around itself therefore you may want to create an FXVerticalFrame to use as the parent of the table You should zero out the padding in the frame so that the frame wraps tightly around the table number of visible rows and columns The number of rows and columns that will be visible when the table is first displayed If the number of visible rows or columns is less than the total number of rows or columns in the table the appropriate scroll bars are displayed TABLE WIDGET number of rows and columns The number of rows and columns to be created when the table is created These numbers include leading rows and columns If the size of the table is fixed you specify the total number of rows and columns If the size of the table is dynamic you specify 1 row and 1 column plus any leading rows or columns and allow the user to add rows or columns as necessary target and selector You can specify a target and selector in the table constructor arguments A table is generally connected to an AFXTableKeyword with a selector of 0 unless the tabl
68. _BOXES Show boxes when item can expand TREELIST_ROOT_BOXES Show root item boxes also The following statements show an example of creating a tree vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 tree FXTreeList vf 5 None 0 LAYOUT FILL X LAYOUT_FILL_Y TREELIST SHOWS BOXES TREELIST ROOT BOXES TREELIST_SHOWS_ LINES TREELIST_BROWSESELECT You add an item to a tree by supplying a parent and a text label You begin by adding root items to the tree Root items have a parent of None The ABAQUS GUI Toolkit provides several ways of adding items to a tree however the most convenient approach uses the addItemLast method as shown in the following example vf FXVerticalFrame gb FRAME _SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 self tree FXTreeList vf 5 None 0 LAYOUT FILL X LAYOUT FILL Y TREELIST_SHOWS_BOXES TREELIST_ROOT_BOXES TREELIST_SHOWS_ LINES TREELIST_BROWSESELECT optionl self tree addItemLast None Option 1 self tree addItemLast optionl Option la self tree addItemLast optionl Option 1b option2 self tree addItemLast None Option 2 self tree addItemLast option2 Option 2a option2b self tree addItemLast option2 Option 2b self tree addItemLast option2b Option 2bi 3 15 TREE WIDGETS option3 self tree addItemLast None Option 3 Option la Option 1b 2 Option 2 Option 2a E Option 2b Option 2bi Option 3
69. a command string that is sent to the kernel for processing For the command to be recognized on the kernel side the appropriate kernel module must have been imported before the command was sent When a GUI module is loaded for the first time a special method named getKernellnitializationCommand is executed This method is empty in the base class implementation and it is up to you to write a method that returns the proper command that will import the appropriate modules on the kernel side The appropriate modules include any module SWITCHING TO A GUI MODULE 8 2 8 3 8 4 for which your GUI module can issue commands If more than one module is required you can separate the statements by semi colons or n characters To avoid name space conflicts with modules loaded by ABAQUS you should use the import moduleName style for importing modules and not the from moduleName import style as shown in the example in GUI module example Section 8 2 7 Instantiating the GUI module The final step in the module GUI code is to construct the module You can construct the module by calling the module constructor at the end of the module GUI file This will construct all the objects defined in the constructor body For example MyModuleGui Registering a GUI module To make a GUI module accessible to the GUI infrastructure you must register the module in the main window code The register command takes two arguments one for the name
70. aGreen3 FXRGB 67 205 128 SeaGreen4 FXRGB 46 139 87 Seashell FXRGB 255 245 238 Seashell1 FXRGB 255 245 238 B 21 APPENDIX B COLORS AND RGB VALUES String RGB value Seashell2 FXRGB 238 229 222 Seashell3 FXRGB 205 197 191 Seashell4 FXRGB 139 134 130 Sienna FXRGB 160 82 45 Siennal FXRGB 255 130 71 Sienna2 FXRGB 238 121 66 Sienna3 FXRGB 205 104 57 Sienna4 FXRGB 139 71 38 SkyBlue FXRGB 135 206 235 SkyBluel FXRGB 135 206 255 SkyBlue2 FXRGB 126 192 238 SkyBlue3 FXRGB 108 166 205 SkyBlue4 FXRGB 74 112 139 SlateBlue FXRGB 106 90 205 SlateBluel FXRGB 131 111 255 SlateBlue2 FXRGB 122 103 238 SlateBlue3 FXRGB 105 89 205 SlateBlue4 FXRGB 71 60 139 SlateGray FXRGB 112 128 144 SlateGray 1 FXRGB 198 226 255 SlateGray2 FXRGB 185 211 238 SlateGray3 FXRGB 159 182 205 SlateGray4 FXRGB 108 123 139 SlateGrey FXRGB 112 128 144 Snow FXRGB 255 250 250 Snow1 FXRGB 255 250 250 Snow2 FXRGB 238 233 233 Snow3 FXRGB 205 201 201 B 22 APPENDIX B COLORS AND RGB VALUES String RGB value Snow4 FXRGB 139 137 137 SpringGreen FXRGB 0 255 127 SpringGreen1 FXRGB 0 255 127 SpringGreen2 FXRGB 0 238 118 SpringGreen3 FXRGB 0 205 102 SpringGreen4 FXRGB 0 139 69 SteelBlue FXRGB 70 130 180 SteelBluel FXRGB 99 184 255 SteelBlue2 FXRGB 92 172 238 SteelBlue3 FXRGB 79 148 205 SteelBlue4 FXRGB 54 100 139 Tan FXRGB 210 180 140 Tanl FXRGB 255 165 79 Tan2 FXRGB 238 1
71. adOnlyKw opts patterns patternIndexTgt AFXFileSelectorDialog parent title fileNameKw readOnlyKw opts patterns patternIndexTgt You use the first constructor when you have a form associated with the dialog box that issues a command for example the dialog box that appears when you click File Open Database You use the second constructor when the dialog box collects input from the user to be used in another dialog box For example when printing to a file from the Print dialog box the user is presented with a text field to enter a file name and a Select button The Select button posts a file selection dialog box that returns the selected file to the Print dialog box but does not issue any command If the user clicks OK the file selection dialog box automatically updates the fileNameKw and readOnlyKw arguments In addition when the dialog box is posted it will set the current directory based on the path of the fileNameKw argument This means that the dialog box remembers the last directory visited by the user when the application posts the dialog box again The following flags are available for the opts argument AFXSELECTFILE_EXISTING Allows the selection of an existing file only AFXSELECTFILE_MULTIPLE Allows the selection of multiple existing files only AFXSELECTFILE_DIRECTORY Allows the selection of an existing directory only AFXSELECTFILE_REMOTE_HOST Allows the opening of files on a remote host You specify the pattern
72. ader columns 3 6 4 Justification By default the table displays entries left justified You can change how items are justified by using the following table methods setColumnJustify column justify setItemJustify row column justify If you supply a value of 1 for the column number the setColumn methods apply the setting to all columns in the table The following table shows the possible values for the justify argument Option flag Effect AFXTable LEFT Align items to the left side of the cell AFXTable CENTER Center items horizontally AFXTable RIGHT Align items to the right side of the cell AFXTable TOP Align items to the top of the cell AFXTable MIDDLE Center items vertically AFXTable BOTTOM Align items to the bottom of the cell 3 22 TABLE WIDGET The following example shows how you can change the justification vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 3 4 3 table setLeadingColumns 1 table setLeadingRows 1 table setLeadingRowLabels X tY table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnWidth 0 30 Center all columns table setColumnJustify 1 AFXTable CENTER x Y Figure 3 25 Justified column headings 3 6 5 Editing By default no items in a table are editable To make all items in a table editable you must specify AFXTABLE EDITABLE in the table constructor To change the edita
73. ales Only UNITED STATES ABAQUS East LLC Mid Atlantic Office 114 Zachary Court Forest Hill MD 21050 Tel 1 410 420 8587 Fax 1 410 420 8908 E mail support AbaqusEast com ABAQUS West Inc Southern CA and AZ Office 1100 Irvine Boulevard 248 Tustin CA 92780 Tel 1 714 731 5895 Fax 1 714 242 7002 E mail Info AbaqusWest com FINLAND ABAQUS Finland Oy Tekniikantie 12 FIN 02150 Espoo Tel 358 9 2517 2973 Fax 358 9 2517 2200 E mail abaqus abaqus se UNITED KINGDOM Kent ABAQUS UK Ltd Great Hollanden Business Centre Unit A Mill Lane Underriver Sevenoaks Kent TN15 OSQ Tel 44 1 732 834930 Fax 44 1 732 834720 E mail hotline abaqus co uk ABAQUS South Inc Southeast Office 484 Broadstone Way Acworth GA 30101 Tel 1 770 795 0960 Fax 1 770 795 7614 E mail support AbaqusSouth com ABAQUS West Inc Rocky Mountains Office 6910 Cordwood Ct Boulder CO 80301 Tel 1 303 664 5444 Fax 1 303 200 9481 E mail Info AbaqusWest com INDIA Pune ABAQUS Engineering Analysis Solutions Pvt Ltd C 9 3rd Floor Bramha Estate Kondwa Road Pune 411040 Tel 91 20 30913739 E mail abaqus abaqus co in Preface This section lists various resources that are available for help with using ABAQUS including technical engineering and systems support training seminars and documentation Support ABAQUS Inc offers both technical engineering support and systems support for A
74. alyses If you have concerns about an analysis we suggest that you contact us at an early stage since it is usually easier to solve problems at the beginning of a project rather than trying to correct an analysis at the end Please have the following information ready before calling the technical engineering support hotline and include it in any written contacts e Your site identifier which can be obtained by typing abaqus whereami at your system prompt or by selecting Help On Version from the main menu bar in ABAQUS CAE or ABAQUS Viewer e The version of ABAQUS that are you using The version numbers for ABAQUS Standard and ABAQUS Explicit are given at the top of the data dat file The version numbers for ABAQUS CAE and ABAQUS Viewer can be found by selecting Help On Version from the main menu bar The version numbers for the ABAQUS Interface for MOLDFLOW and the ABAQUS Interface for MSC ADAMS are output to the screen The version number for ABAQUS for CATIA V5 can be found by selecting Help About ABAQUS for CATIA V5 from the main menu bar in either of the ABAQUS for CATIA V5 workbenches e The type of computer on which you are running ABAQUS e The symptoms of any problems including the exact error messages if any e Workarounds or tests that you have already tried When calling for support about a specific problem any available ABAQUS output files may be helpful in answering questions that the support engineer
75. ame capabilities as FXPacker For more information see General purpose layout managers Section 4 5 FXGroupBox Same capabilities as FXPacker but allows a titled border For more information see General purpose layout managers Section 4 5 FXMatrix Arranges widgets in rows and columns For more information see Row and column layout manager Section 4 6 FXSplitter Splits an area vertically or horizontally and allows you to resize the areas For more information see Resizable regions Section 4 7 FXSwitcher Swaps children on top of each other rotating regions For more information see Rotating regions Section 4 8 FXTabBook Displays one tab or one page of widgets at atime The user selects the tab to view by clicking a tab button For more information see Tab books Section 4 9 4 2 Padding and spacing Layout managers and most widgets provide some default padding so that widgets are spaced apart from each other These values are commonly found near the end of the widget s list of arguments For example FXPacker pl pr pt pb In general you should accept the default values for padding However if you have nested layout managers you should set the padding values to zero Layout managers also provide spacing between their children These values are commonly found at the end of the widget s list of arguments For example FXPacker hs vs 4 2 VERTICAL A
76. ased on the setting of two other buttons you can use the processUpdates method to update your GUI The processUpdates method is called during each GUI update cycle so you should not do anything that is time consuming in this method Generally you should perform tasks such as enabling and disabling or showing and hiding widgets For example def processUpdates self if self form kwl getValue 1 and self form kw2 getValue 2 self btnl disable DATA DIALOG BOXES im Part Display Options STOO GTER INES MORE TENGE Style I Show edges in shaded render style M Figure 5 8 An example of using transitions to control how the application stipples widgets else self btnl enable If the tasks you need to perform are time consuming you should write your own message handler that is invoked only upon some specific user action For example if you need to scan an ODB for valid data you could make the commit button of the dialog send a message to your dialog box That message would invoke your message handler that does the scanning That way the scanning occurs only when the user commits the dialog not during every GUI update cycle For more information on message handlers see Targets and messages Section 6 4 4 5 16 COMMON DIALOG BOXES 5 6 7 Action area The AFXDataDialog class provides standard handling for all the buttons that can appear in the action area Table 5 2 shows the action that t
77. ate an action area for example in a toolbox dialog box You can also specify whether a separator should be placed between the action area and the rest of the dialog box by including the following flag in the options DIALOG_ACTIONS_SEPARATOR The style in ABAQUS CAE is to omit a separator if there is already delineation between the action area and the rest ofthe dialog box for example a frame that stretches across the entire width ofthe dialog box along the bottom of the dialog box The following statements illustrate how you define an action area in a dialog box with a separator class ActionAreaDB AFXDialog def _ init _ self AFXDialog init self Action Area Example 1 self OK self APPLY self CANCEL DIALOG ACTIONS SEPARATOR FXLabel self Standard action area example dialog Action Area Example 1 x Standard action area example dialog OK Apply Cancel Figure 5 4 An example of a standard action area 5 5 5 Custom action area button names The flags in Table 5 1 cover all the semantics you might need in a dialog box As a result there is no need for any additional custom flags however there may be cases where you want to use a different label for one of the standard actions To use a different label for one of the standard actions you do not specify CUSTOM DIALOG BOXES any button flags in the constructor arguments however you use the appendActionButton method to add your own action area buttons
78. ateGray2 DarkSlateGray3 DarkSlateGray4 DarkSlateGrey DarkTurquoise DarkViolet DeepPink DeepPink1 DeepPink2 DeepPink3 DeepPink4 DeepSkyBlue DeepSkyBlue1 DeepSkyBlue2 DeepSkyBlue3 DeepSkyBlue4 DimGray DimGrey DodgerBlue DodgerBlue1 DodgerBlue2 DodgerBlue3 DodgerBlue4 Firebrick Firebrick1 Firebrick2 Firebrick3 FXRGB 151 255 255 FXRGB 141 238 238 FXRGB 121 205 205 FXRGB 82 139 139 FXRGB 47 79 79 FXRGB 0 206 209 FXRGB 148 0 211 FXRGB 255 20 147 FXRGB 255 20 147 FXRGB 238 18 137 FXRGB 205 16 118 FXRGB 139 10 80 FXRGB 0 191 255 FXRGB 0 191 255 FXRGB 0 178 238 FXRGB 0 154 205 FXRGB 0 104 139 FXRGB 105 105 105 FXRGB 105 105 105 FXRGB 30 144 255 FXRGB 30 144 255 FXRGB 28 134 238 FXRGB 24 116 205 FXRGB 16 78 139 FXRGB 178 34 34 FXRGB 255 48 48 FXRGB 238 44 44 FXRGB 205 38 38 B 5 APPENDIX B COLORS AND RGB VALUES String RGB value Firebrick4 FXRGB 139 26 26 Floral White FXRGB 255 250 240 ForestGreen FXRGB 34 139 34 Gainsboro FXRGB 220 220 220 GhostWhite FXRGB 248 248 255 Gold FXRGB 255 215 0 Gold1 FXRGB 255 215 0 Gold2 FXRGB 238 201 0 Gold3 FXRGB 205 173 0 Gold4 FXRGB 139 117 0 Goldenrod FXRGB 218 165 32 Goldenrod1 FXRGB 255 193 37 Goldenrod2 FXRGB 238 180 34 Goldenrod3 FXRGB 205 155 29 Goldenrod4 FXRGB 139 105 20 Gray FXRGB 190 190 190 Gray0 FXRGB 0 0 0 Grayl FXRGB 3 3 3 Gray10 FXRGB 26 26 26 Gray 100
79. bility of some items in a table you can use the following table methods setColumnEditable column TRUE FALSE setItemEditable row column TRUE FALSE 3 6 6 Types By default all items in a table are text items However the table widget also supports the other types of items shown in the following table 3 23 TABLE WIDGET Type Effect TEXT Item shows text a text field is used to edit the value LIST Item shows text a combo box is used to edit the value BOOL Item shows an icon clicking on it toggles between a true and false icon ICON Item shows an icon it is not editable COLOR Item shows a color button You can change the type of a column or the type of an individual item using the following table methods setColumnType column type setItemType row column type 3 6 7 List type If you want to allow the user to specify a value in a column by selecting from a list of items you must first set the column to be oftype LIST You then create a list and assign it to that column When the user clicks on an item in that column the table will display a noneditable combo box that contains the entries from the list The following example illustrates how you can create a combo box within a table cell vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 AFXTABLE_NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table setLeadingR
80. button Once a mode is activated it is responsible for gathering user input processing the input sending a command and performing any error handling associated with the mode or the commands it sends For a detailed discussion of modes see Chapter 7 Modes The ABAQUS GUI toolkit provides two modes Form modes Form modes provide an interface to dialog boxes Form modes gather input from the user using one or more dialog boxes Procedure modes Procedure modes provide an interface that guides the user through a sequence of steps by prompting for input in the prompt area of the application method A String specifying the method of the kernel command objectName A String specifying the object of the kernel command GUI COMMANDS registerQuery A Boolean specifying whether or not to register a query on the object For example the following statement creates a command to edit graphics options cmd AFXGuiCommand self setValues session graphicsOptions TRUE If you have more than one GUI command in a mode the commands are processed in the same order in which they are created in the mode For more examples of creating GUI commands see Form example Section 7 3 1 and Procedure example Section 7 4 1 6 4 2 GUI commands and current objects Most commands in ABAQUS CAE operate on the current object for example the current viewport or the current part As a convenience modes recognize a special
81. call when a message of a certain type and ID is received These concepts are illustrated in Figure 6 2 The message map is defined by using the FXMAPFUNC function see example below This macro takes four arguments self message type message ID and method name The method name must be qualified by the class name className methodName When a message is received whose type and ID match those defined in an FXMAPFUNC entry the corresponding method will be called If you have a GUI COMMANDS Object 3 ID_1 msgType1 Object 1 Target None Obi Msg ID 0 ea Da Msg Types Various Msg Types Various Message Map msgType1 ID_1 onCmdA msgType2 ID_2 onCmdB Object 2 msgTypet ID_3 onCmdA ID_2 msgType2 Target Object 3 onCmdA Msg ID ID_2 Do something Msg Types Various onCmaB Do something Figure 6 2 Targets and messages large range of IDs that you want to define in the message map you can use the FXMAPFUNCS function which takes one additional argument self message type start message ID end message ID and method name Objects react to messages using message handlers All message handlers have the same prototype which contains the following e The sender of the message e The message selector e Some user data You can extract the type and ID of the message from the selector using the SELTYPE and SELID functions The following code shows how message maps message IDs
82. controls the settings of all the children of the branch if the branch is toggled off all the children are toggled off and vice versa For example tree AFXOptionTreeList parent 6 tree addItemLast Item 1 item tree addItemLast Item 2 item addItemLast Item 3 item addItemLast Item 4 item addItemLast Item 5 I Item 1 w V Item2 T Item 3 M Item 4 T Item 5 Figure 3 20 An example of an option tree list from AFXOptionTreeList Table widget The AFXTable widget arranges items in rows and columns similar to a spreadsheet The table can have leading rows and columns which serve as headings Figure 3 21 shows an example of how the ABAQUS GUI Toolkit lays out a table The AFXTable widget has many options and methods that allow a lot of flexibility when you are trying to configure a table for specific purposes These options and methods are discussed in the following sections The following topics are covered e Table constructor Section 3 6 1 e Rows and columns Section 3 6 2 e Spanning Section 3 6 3 e Justification Section 3 6 4 TABLE WIDGET leading row x Y items leading column Figure 3 21 The layout of a table e Editing Section 3 6 5 e Types Section 3 6 6 e List type Section 3 6 7 e Boolean type Section 3 6 8 e Icon type Section 3 6 9 e Popup menu Section 3 6 11 e Colors Section 3 6 12 3 6 1 Table constructor The AF
83. ct in the vertical direction FXPacker FXTopWindow and FXGroupBox must use LAYOUT _LEFT and LAYOUT_RIGHT with LAYOUT _SIDE TOP and LAYOUT SIDE BOTTOM The ABAQUS GUI Toolkit ignores hints if they do not make sense for example FXHorizontalFrame ignores LAYOUT TOP and LAYOUT BOTTOM Similar rules apply for the other hints LAYOUT EXAMPLES 4 11 Layout examples The following examples create three buttons one at a time using the default layout hints As each button is created the figures show the effect on the space remaining in the layout cavity Example 1 The first example starts by creating a single button on the left side of the cavity The default value for the vertical position is LAYOUT_TOP so the example places the button on the left side and at the top of the available space gb FXGroupBox parent FXButton gb Button 1 opts LAYOUT_SIDE_LEFT BUTTON_NORMAL Space available for re maining children Figure 4 8 Creating a button on the left side and at the top of the layout cavity The following statement adds a second button on the left side at the top of the available space FXButton gb Button 2 opts LAYOUT_SIDE_LEFT BUTTON_NORMAL as aaa A Button 1 Button 2 Space available for re maining children Figure 4 9 Adding a second button on the left side at the top of the layout cavity The following statement adds a third button on the left side at the top of the available space
84. ctors of all the widgets required to build the initial structure of an application by constructing the main window The script then calls the application object s create method This call traverses the entire widget hierarchy calling the create method of each widget For more information and an example script see Startup script Section 11 2 If you create widgets after the startup script has called the application s create method the create method must be called on those new widgets otherwise they will not be visible on the screen If your dialog box is posted by a form or by a procedure the infrastructure calls the create method on the dialog box However if you post a dialog box yourself you must call the create method on the dialog box before you call its show method Similarly if you construct icons that are used after a widget has been created you must call the create method on those icons before using them in a widget For example if you want to change a label s icon after it has already been shown in a dialog box you must do the following 1 Construct the new icon 2 Call the new icon s create method 3 Pass the icon to the label using the label s setIcon method 3 9 Widgets and fonts When the user starts an application it sets the default font to be used for all widgets On Windows platforms the application obtains the default font from the desktop settings On Linux platforms the default f
85. d you can redefine some of the methods to customize the behavior of the mode The following list describes each of the methods called by the mode verifyKeywordValues The verifyKeywordValues method calls the verify method for each keyword of each command associated with the mode and posts an error dialog box if necessary The verifyKeywordValues method returns TRUE if no errors were encountered otherwise it returns FALSE and terminates further command processing doCustomChecks The doCustomChecks method has an empty implementation in the base class You can redefine this method to perform any additional checking of keyword values typically to perform range checking or to check some interdependency between values The doCustomChecks method should return TRUE if no errors were encountered otherwise it returns FALSE so that further command processing will be terminated The doCustomChecks method is called by the mode during step and dialog box processing and during command processing issueCommands The issueCommands method calls the following methods e getCommandString This method returns a string that represents the commands collected from each command associated with the mode Required keywords are always sent with the command but optional keywords are sent only if their value has changed The commands are issued to the kernel in the same order as the commands were constructed in the mode If your command does not fit the standard st
86. d before returning the dialog box as shown in Procedure example Section 7 4 1 7 4 4 getNextStep If your mode contains more than one step you must write the getNextStep method in addition to the getFirstStep method The previous step is passed into the getNextStep method so that you can determine where the user is in the sequence of steps and act accordingly The getNextStep method should return the next step in the sequence or it should return None to indicate that it has finished collecting input from the user The following example which is a modified version of the example in Procedure example Section 7 4 1 illustrates how inputs are collected from the user in a series of three steps rather than just one Hawa w w w w w m a m a m m m a m a m m m a y a a m m a ay ay m m m a y ay y m m a ay y y m ma a ey y y m ma a ey y y a ma a y y N a a aa def getFirstStep self self cmd setKeywordValuesToDefaults self plateWidthDB None self plateHeightDB None db PlateNameDB self self stepl AFXDialogStep self db return self stepl Innnnnannnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn def getNextStep self previousStep if previousStep self stepl if not self plateWidthDB self plateWidthDB PlateWidthDB self self step2 AFXDialogStep self self plateWidthDB return self step2 elif previousStep self step2 7 12 PROCEDURE MODES if not self plateHeightDB self plateHeightDB
87. d by using the setSelBackColor method If you do not want the colors to change when the user selects an item you can set the colors used for items that are selected to be the same as the colors used for items that are not selected This approach is shown in the following example itemColor table getItemBackColor 1 1 table setSelBackColor itemColor itemTextColor table getItemTextColor 1 1 table setSelTextColor itemTextColor You can set colors using the color name or by specifying RGB values using the FXRGB function For a list of valid color names and their corresponding RGB values see Appendix B Colors and RGB values Both methods are illustrated in the following example 3 30 TABLE WIDGET Copy amp Paste Insert Row Before Insert Row After x Delete Rows Clear Contents Clear Table a Read from File Figure 3 31 Popup menu options vf FXVerticalFrame parent FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 AFXTABLE_NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table setLeadingRowLabels Name tDescription table showHorizontalGrid TRUE table showVerticalGrid TRUE table setItemTextColor 1 0 Blue table setItemTextColor 1 1 FXRGB 0 0 255 table setItemBackColor 3 0 Pink table setItemBackColor 3 1 FXRGB 255 192 203 Name Description Part 1 Solid extrusion Part 2 2D planar Part 3 Axisymmetric
88. d to customers who subscribe to either the Nuclear QA Program or the Quality Monitoring Service Update Information e ABAQUS Release Notes This document contains brief descriptions of the new features available in the latest release of the ABAQUS product line Programming e ABAQUS Scripting Users Manual This online only manual provides a description of the ABAQUS Scripting Interface The manual describes how commands can be used to create and analyze ABAQUS CAE models to view the results of the analysis and to automate repetitive tasks It also contains information on using the ABAQUS Scripting Interface or C as an application programming interface API to the output database e ABAQUS Scripting Reference Manual This online only manual provides a command reference that lists the syntax of each command in the ABAQUS Scripting Interface e ABAQUS GUI Toolkit User s Manual This online only manual provides a description of the ABAQUS GUI Toolkit The manual describes the components and organization of the ABAQUS GUI It also describes how you can customize the ABAQUS GUI to build a particular application e ABAQUS GUI Toolkit Reference Manual This online only manual provides a command reference that lists the syntax of each command in the ABAQUS GUI Toolkit Interfaces e ABAQUS Interface for MSC ADAMS User s Manual This document describes how to use the ABAQUS Interface for MSC ADAMS which creates ABAQUS models of MSC ADAMS comp
89. dal For example mainWindow getAFXApp getAFXMainWindow showAFXInformationDialog mainWindow This is an information dialog CUSTOM DIALOG BOXES ml Mold Designer x This is an information dialog Figure 5 3 An example of an information dialog box from showAFXInformationDialog 5 4 4 Specialized message dialog boxes If you need more flexibility than the standard message dialog boxes you must derive a new dialog box from AFXDialog and provide the specialized handling For more information see Custom dialog boxes Section 5 5 5 5 Custom dialog boxes AFXDialog is the base class for the other dialog box classes in the toolkit If none of the other dialog box classes suit your needs you must derive your dialog box from AFXDialog and provide most of the dialog processing yourself This section describes how you can use AFXDialog to create custom dialog boxes The following topics are covered e An overview of custom dialog boxes Section 5 5 1 e Constructors Section 5 5 2 e Sizing and location Section 5 5 3 e Action area Section 5 5 4 e Custom action area button names Section 5 5 5 e Action button handling Section 5 5 6 5 5 1 An overview of custom dialog boxes AFXDialog is the base class for the other dialog box classes in the toolkit If none of the other dialog box classes suit your needs you must derive your dialog box from AFXDialog and provide most of
90. date all its children Conversely if you specify opts MATRIX_BY COLUMNS the matrix will create the specified number of columns and as many rows as are needed to accommodate all its children For example using the default opts MATRIX BY ROWS setting m FXMatrix parent 2 FXButton m FXButton m FXButton m FXButton m FXButton m FXButton m 4 7 Resizable regions Button Button Button Button Button Button 1 2 3 4 5 6 u m m un Button 1 Button 3 Button 5 Button 2 Button al Button e Figure 4 4 An example of a matrix with two rows from FXMatrix The FXSplitter widget splits an area vertically or horizontally The user can drag the cursor on the region between the areas and resize the areas For example 4 5 ROTATING REGIONS sp FXSplitter parent LAYOUT_FILL_X LAYOUT_FIX_HEIGHT SPLITTER_VERTICAL 0 0 0 100 hfl FXHorizontalFrame sp FRAME SUNKEN FRAME THICK FXLabel hf1 This is area 1 hf2 FXHorizontalFrame sp FRAME SUNKEN FRAME THICK FXLabel hf2 This is area 2 This is area 1 This is area 2 Figure 4 5 An example of resizable areas laid out vertically by FXSplitter 4 8 Rotating regions The FXSwitcher widget manages children that are positioned on top of each other FXSwitcher allows you to select which child should be shown by either sending it a message or calling its setCurrent method When sending a message you must set the message ID to FXSwi
91. dget supports a read only state through the setReadOnlyState method For example tf AFXTextField parent 8 String AFXTextField in read only mode keyword tf setReadOnlyState TRUE 3 2 2 Multi line text widget FXText provides a multi line text entry area For example text FXText parent None 0 LAYOUT_FIX_WIDTH LAYOUT FIX HEIGHT 0 0 300 100 text setText This is an FXText widget This is an FXText widget A D gt Figure 3 13 An example of a multi line text entry area from FXText 3 9 LISTS AND COMBO BOXES 3 3 Lists and combo boxes This section describes the widgets in the ABAQUS GUI Toolkit that allow you to choose one or more items from a list e You use a list widget when there is enough room in the GUI and when it is helpful to display all or most of the choices at the same time e You use a combo box to conserve space in the GUI and when it is preferable to display only the current choice The following topics are covered e Lists Section 3 3 1 e Combo boxes Section 3 3 2 e List boxes Section 3 3 3 3 3 1 Lists AFXList allows one or more selections from its items AFXList extends the capabilities of FXList by providing the ability to set and update its value based on the user data passed in with the items in the list In most cases the user data are symbolic constant IDs The list created by AFXList supports the following selection policies LIST_SINGLESELECT The us
92. dialog box For example try the following e Click the D icon to post the dialog box and note the text labels shown in the dialog box e Click Cancel in the dialog box to unpost it e Change one of the labels in testDB py and save the file RUNNING THE PROTOTYPE APPLICATION e Click the D icon to post the dialog box again You will see the modified label in the dialog box When you click OK in the dialog box the kernel command issued by the dialog box is written to the message area rather than being executed by ABAQUS CAE This allows you to debug the command before you try to execute it in the kernel After you have debugged your form and dialog box code you can modify the form to issue the command to the kernel by following the example in Form example Section 7 3 1 You can connect the form to your GUI instead of to the F icon by following the example shown in GUI module example Section 8 2 Part Ill Building dialog boxes This part describes the components of a dialog box and how you create the components using the ABAQUS GUI Toolkit The following topics are covered e Chapter 3 Widgets e Chapter 4 Layout managers e Chapter 5 Dialog boxes LABELS AND BUTTONS Widgets This section describes how you can create widgets in your application There are many widgets in the ABAQUS GUI Toolkit however only the most commonly used widgets are described here You should refer to the ABAQUS GUI
93. dialog box that needs the queries Similarly you unregister queries within the hide method that you write for your dialog box In the following example if the user creates deletes renames or edits a part the application will call the onPartsChanged method and update the dialog box class MyDialog AFXDataDialog def onPartsChanged self Code to update the part list in the dialog box def show self from kernelAccess import mdb mdb models Model 1 parts registerQuery self onPartsChanged AFXDataDialog show self def hide self from kernelAccess import mdb mdb models Model 1 parts unregisterQuery self onPartsChanged AFXDataDialog hide self 6 7 3 Recognizing when custom kernel data change To receive notification in the GUI of changes made to custom kernel objects those kernel objects must make use of special classes provided by the customKernel module The customKernel module provides the following special classes all of which are capable of notifying the GUI when the contents of the class changes e CommandRegister allows you to create general classes For more information see CommandRegister class Section 5 6 3 of the ABAQUS Scripting User s Manual e RepositorySupport allows you to create repositories below other repositories For more information see RepositorySupport Section 5 6 6 of the ABAQUS Scripting User s Manual 6 21 RECEIVING NOTIFICATION OF KERNEL DAT
94. ds For more information see Keeping the GUI and commands up to date Section 6 4 3 If there is no kernel object associated with your command for example when creating a new object you can set the keyword values by specifying a default value in their constructor If you have a default object that you want to use to reestablish default values for a dialog box you can use the mode s registerDefaultsObject method to register an object whose values will be queried when the user presses the Defaults button in the dialog box For more information see Defaults objects Section 6 4 15 By default dialog boxes are posted as modeless You can post a dialog box as modal by calling self setModal TRUE In most cases you setthe modality only once in the mode however you can change the modality as often as needed by calling the setModal method in the getFirstDialog or getNextDialog methods For more information see Modal versus modeless Section 5 2 7 11 PROCEDURE MODES 7 4 3 getFirstStep You must always write the getFirstStep method for your mode The getFirstStep method should return the first step of the mode In Procedure example Section 7 4 1 a pointer to the procedure is passed into the dialog box constructor The dialog box will use this pointer to access the mode s keywords If you want the same default values to appear every time you post the dialog box you must call the setKeywordValuesToDefaults metho
95. e GUI class that provides most of the functionality that you want you can begin by deriving from that class and then making modifications For more information see Chapter 10 Customizing an existing module or toolset The following example shows how to create a new toolset class by deriving from AFXToolsetGui from abaqusGui import class MyToolsetGui AFXToolsetGui 9 1 REGISTERING TOOLSETS 9 3 9 4 Innnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn def _ init self Construct the base class AFXToolsetGui init self toolsetName In the constructor of the new class you call the constructor of the base class The AFXToolsetGui class takes the following argument toolsetName A String specifying the name of the toolset The toolset name provides an identifier for the toolset Creating toolset components You create menu toolbar and toolbox items in a toolset in the same way that you create those items in a module When you create menu toolbar and toolbox items in a module the module is used as the parent In contrast when you create a toolset component such as menu panes the toolset is used as the parent of the toolset component The toolset is used as the parent because the components need to be managed by the toolset when the the toolset is swapped in and out of the GUI For more information on creating these components see Chapter 8 Creating a GUI module Registering toolsets Y
96. e has columns that are not directly related to the data required by the command to be sent to the kernel in that case the dialog may be specified as the target so the data in the table can be processed appropriately by opts your code The option flags that you can specify in the table constructor are shown in the following table Option flag Effect AFXTABLE NORMAL default AFXTABLE COLUMN RESIZABLE AFXTABLE ROW_RESIZABLE AFXTABLE RESIZE AFXTABLE NO COLUMN SELECT AFXTABLE NO ROW_ SELECT AFXTABLE SINGLE SELECT AFXTABLE BROWSE SELECT AFXTABLE ROW MODE AFXTABLE EDITABLE AFXTABLE COLUMN RE SIZABLE LAYOUT FILL X LAYOUT FILL Y Allows columns to be resized by the user Allows rows to be resized by the user AFXTABLE_COLUMN_RESIZABLE AFXTABLE ROW_RESIZABLE Disallows selecting the entire column when its heading is clicked Disallows selecting the entire row when its heading is clicked Allows up to one item to be selected Enforces one single item to be selected at all times Selecting an item in a row selects the entire row Allows all items in the table to be edited TABLE WIDGET By default the user can select multiple items in a table To change this behavior you should use the appropriate flag to specify either single select mode or browse select mode In addition you can specify whether the entire row should be selected when the user selects any item in the row
97. e provide the output from abaqus info support It is important that you provide as much information as possible about your problem error messages from an aborted analysis output from the abaqus info support command etc ABAQUS Web server For users connected to the Internet many questions can be answered by visiting the ABAQUS Home Page on the World Wide Web at http www abaqus com The information available on the ABAQUS Home Page includes e Link to the AOSS e ABAQUS systems information and computer requirements e ABAQUS performance data e Error status reports e ABAQUS documentation price list e Training seminar schedule e ABAQUS Insights newsletter e Technology briefs Anonymous ftp site For users connected to the Internet ABAQUS maintains useful documents on an anonymous ftp account on the computer ftp abaqus com Simply ftp to ftp abaqus com Login as user anonymous and type your e mail address as your password Directions will come up automatically upon login Writing to technical support Address of ABAQUS Headquarters ABAQUS Inc 166 Valley Street Providence RI 02909 USA Attention Technical Support Addresses for other offices and representatives are listed in the front of each manual Support for academic institutions Under the terms of the Academic License Agreement we do not provide support to users at academic institutions Academic users can purchase technical support on an hourly basis For more in
98. e sendCommand function takes a single argument a string specifying the command to be executed in the kernel For example from abaqusGui import sendCommand sendCommand print this is a test 6 4 GUI commands GUI commands are designed to work together with modes Modes perform the command processing and send the command to the kernel For more information see Chapter 7 Modes This section describes how to construct and use GUI commands The following topics are covered e Constructing GUI commands Section 6 4 1 GUI COMMANDS 6 4 1 You use the AFXGuiCommand class to construct a GUI command The AFXGuiCommand class takes GUI commands and current objects Section 6 4 2 Keeping the GUI and commands up to date Section 6 4 3 Targets and messages Section 6 4 4 Automatic GUI updating Section 6 4 5 Data targets Section 6 4 6 Option versus value mode Section 6 4 7 AFXKeywords Section 6 4 8 Connecting keywords to widgets Section 6 4 9 Boolean integer float and string keyword examples Section 6 4 10 Symbolic constant keyword examples Section 6 4 11 Tuple keyword examples Section 6 4 12 Table keyword example Section 6 4 13 Object keyword example Section 6 4 14 Defaults objects Section 6 4 15 Constructing GUI commands the following arguments mode Modes are activated through a control in the GUI typically a menu
99. e toolkit calls is provided The ABAQUS GUI Toolkit is based on the FOX GUI toolkit While this manual explains some of the basic concepts of the FOX toolkit it does not provide details for many other aspects of the Fox toolkit For more details on the FOX GUI toolkit refer to the FOX web site This manual consists of the following sections Widgets This section describes some of the most commonly used widgets in the ABAQUS GUI Toolkit Layout managers This section describes how to use the various layout managers in the ABAQUS GUI Toolkit to arrange widgets in a dialog box Dialog boxes This section describes the dialog boxes that you can create using the ABAQUS GUI Toolkit Commands In an application that employs a graphical user interface the interface must collect input from the user and communicate that input to the application In addition the graphical user interface must keep its state up to date based on the state of the application This section describes how ORGANIZATION OF THE ABAQUS GUI Toolkit USER S MANUAL those tasks are accomplished using the ABAQUS GUI Toolkit and the two types of commands in ABAQUS CAE kernel commands and GUI commands Modes A mode is a mechanism for gathering input from the user processing that input and then issuing a command to the kernel This section describes the modes that are available in the ABAQUS GUI Toolkit Creating a GUI module This section describes how you can create a
100. eSwitch 9 9 1 9 2 GUI TOOLSET EXAMPLE Creating a GUI toolset Toolsets are similar to modules except that they can be used in more than one module Toolsets typically have less functionality than modules because toolsets specialize in performing a specific task such as partitioning This section describes how you can create a GUI toolset The following topics are covered e An overview of creating a GUI toolset Section 9 1 e GUI Toolset example Section 9 2 e Creating toolset components Section 9 3 e Registering toolsets Section 9 4 An overview of creating a GUI toolset To create a new GUI toolset you must follow these steps e Derive a new class from a toolset base class e Create menus in the menu bar This step is optional e Create items in the Tools menu This step is optional e Create buttons in the toolbar This step is optional e Create buttons in the toolbox This step is optional e Create modes to collect input from the user and to issue commands GUI Toolset example The AFXToolsetGui base class provides various toolset infrastructure support functions For example the AFXToolsetGui base class keeps track of the menus in a toolset along with the toolbar and toolbox buttons so that they can be swapped in and out automatically as the user changes modules To create your own toolset GUI you begin by deriving from the AFXToolsetGui class Alternatively if there is another modul
101. ed until the first time the user visits that module The order in which the modules are registered is the order in which the modules will appear in the Module combo box in the context bar To register a module you call the registerModule method The registerModule method takes the following arguments displayedName A string that the application will display in the Module combo box in the context bar moduleName A string that specifies the name of the module to be loaded It is your responsibility to ensure that this name is the same as your GUI module file name without the py extension For more information see Instantiating the GUI module Section 8 2 7 14 4 APPENDIX A ICONS Appendix A Icons The ABAQUS GUI Toolkit supports only the XPM pixmap image format for creating icons The format of a pixmap icon is simple and you can use any pixmap editor or even a text editor to create the icon data For more details on the XPM format visit the XPM web site The following image editing programs support the XPM format e ImageMagick www imagemagick org e The GIMP www gimp org You can also find references to pixmap editors in the FAQ page on the XPM web site Once you have defined the XPM image data the data can be used to create an icon as shown in the following example Note For a list of valid color names and their corresponding RGB values see Appendix B Colors and RGB values To define a transparent color
102. eft side of the cavity LAYOUT_SIDE_RIGHT Attaches a widget to the right side of the cavity You should specify only one of the LAYOUT SIDE hints per child The top and bottom hints effectively reduce the height of the available space remaining to place other children The left and right hints effectively reduce the width of the available space remaining to place other children All layout managers support the following layout hints e LAYOUT LEFT default and LAYOUT RIGHT The layout manager places the widget on the left or right side of the space remaining in the container e LAYOUT_TOP default and LAYOUT_BOTTOM The layout manager places the widget on the top or bottom side of the space remaining in the container e LAYOUT CENTER X and LAYOUT_CENTER_Y The layout manager centers the widget in the X or Y direction in the parent The manager adds extra spacing around the widget to place it at the center of the space available to it The widget s size will be its default size unless you specify LAYOUT FIX WIDTH or LAYOUT _FIX HEIGHT e LAYOUT FILL_X and LAYOUT FILL_Y You can specify either none one or both of these layout hints LAYOUT _FILL_X causes the parent layout manager to stretch or to shrink the widget to accomodate the available space If you place more than one child with this option side by side the manager subdivides the available space proportionally to the children s default size LAYOUT FILL_Y has the identical effe
103. el Create toolbox icons group AFXToolboxGroup self AFXToolButton group tMy Module nToolbox Button icon sel 3 1 9 Flyout buttons The AFXFlyoutButton widget displays a flyout popup window The flyout popup window contains AFXFlyoutItem widgets and appears when the user presses mouse button 1 on the button and holds down mouse button 1 for a certain time span If the user simply clicks mouse button 1 quickly on the button the flyout popup window will not be displayed and the flyout button will act just like a regular button The AFXFlyoutButton widget displays the icon of the current target along with a right triangle in the lower right corner to indicate that a flyout popup window can be invoked For example group AFXToolbarGroup self popup AFXPopup self getAFXApp getAFXMainWindow TEXT WIDGETS AFXFlyoutItem popup tFlyout Button 1 squarelcon AFXFlyoutItem popup tFlyout Button 2 circlelcon AFXFlyoutItem popup tFlyout Button 3 trianglelcon AFXFlyoutButton group popup popup create Flyout Button 2 Figure 3 8 An example of flyout buttons from AFXFlyoutItem 3 1 10 Color buttons The AFXColorButton widget displays a push button that shows a color Clicking the button posts the color selection dialog box which the user can use to change the value of the color for the button For example AFXColorButton parent Color Color u Figure 3 9 An example of an AFXColorButt
104. elements in the same step There is no control for iso lines ABAQUS always displays iso lines when the user is picking faces There is no support for unselecting entities that belong to selected entities For example when the user selects a face ABAQUS also selects all the edges belonging to the selected face The user cannot unselect one of those edges Probing is not supported These limitations may be removed in a future release of the ABAQUS GUI Toolkit 7 18 Part VI GUI modules and toolsets This part describes how you can create your own modules and toolsets This part also describes how you can modify an existing ABAQUS CAE module or toolset The following topics are covered e Chapter 8 Creating a GUI module e Chapter 9 Creating a GUI toolset e Chapter 10 Customizing an existing module or toolset 8 GUI MODULE EXAMPLE Creating a GUI module This section describes how you can create a GUI module The following topics are covered 8 1 An overview of creating a GUI module Section 8 1 GUI module example Section 8 2 Deriving a new module class Section 8 2 1 Menu bar items Section 8 2 2 Toolbar items Section 8 2 3 Toolbox items Section 8 2 4 Registering toolsets Section 8 2 5 Kernel module initialization Section 8 2 6 Instantiating the GUI module Section 8 2 7 Switching to a GUI module Section 8 4 An overview of creat
105. elf app windowTitle fileToolset FileToolsetGui self printForm fileToolset getPrintForm self registerToolset fileToolset GUI_IN MENUBAR GUI_IN_ TOOLBAR Then you can use the print form in your dialog box class as shown below printForm getAFXApp getAFXMainWindow printForm COMMON DIALOG BOXES FXButton parent Print None printForm AFXMode ID_ACTIVATE To access the print form you must construct and register the file toolset However you cannot access the print form from within a plug in As a result you can only use the approach described here in a customized application 5 7 3 Color selector dialog box The AFXColorSelector widget provides the ability to choose a color from a predefined palette of colors This dialog box is posted by an AFXColorButton For more information see Color buttons Section 3 1 10 5 20 Part IV Issuing commands This part describes how a dialog box can issue commands to the ABAQUS CAE kernel The following topics are covered e Chapter 6 Commands e Chapter 7 Modes THE KERNEL AND GUI PROCESSES 6 Commands This section describes the role of commands in the ABAQUS GUI toolkit The following topics are covered e An overview of commands Section 6 1 e The kernel and GUI processes Section 6 2 e Kernel commands Section 6 3 e GUI commands Section 6 4 e AFXTargets Section 6 5 e Accessing ker
106. elf self ID_OVERWRITE SEL_COMMAND MyForm onCmdOverwrite def doCustomChecks self import os if os path exists self fileNameKw getValue db self getCurrentDialog showAFXWarningDialog db File already exists n nOK to overwrite AFXDialog YES AFXDialog NO self self ID_OVERWRITE return FALSE return TRUE def onCmdOverwrite self sender sel ptr if sender getPressedButtonId AFXDialog ID_ CLICKED YES AFXForm issueCommands self return 1 Normally the GUI infrastructure will take care of sending commands to the kernel but there may be cases where you want to send a command directly You can send a command to the kernel using the 7 5 MODE PROCESSING sendCommand cmd method which takes a single argument that is the command string to be sent However no error handling is available when using this method even if you wrap this method in a try block any exception thrown by the command on the kernel side will not be trapped in your GUI code 7 2 5 Work in progress If the command sent to the kernel takes more than a certain amount of time approximately one second the GUI will lock and the busy cursor will be displayed If you want to provide additional feedback about the progress of your command you can add work in progress commands to your kernel code For more information see Status commands Section 47 6 of the ABAQUS Scripting Reference Manual The following statements illustrate how you can u
107. en modules and toolsets You can provide a user interface that is launched from the Plug ins menu If you intend to add only some utility functions to ABAQUS CAE using the plug in approach will probably meet your needs Plug ins are described in detail in Part VIII Using plug ins of the ABAQUS CAE User s Manual Customized applications Creating a customized application allows you to build the application from the ground up In addition a customized application provides control over which modules and toolsets are available in the application If you intend to build a vertical application an application intended for a very specific use you should create a custom application While creating a custom application offers the most flexibility it requires more work than the using ABAQUS CAE plug in architecture 2 3 Running the prototype application A custom application called the prototype application is available from the ABAQUS Process Automation Portal The prototype application allows you to experiment with the contents of your dialog box until you produce a design that is satisfactory You can start the prototype application make changes to the code that controls the contents of the dialog box and instantly see those changes reflected in the application You can access the portal from the ABAQUS CAE Plug ins ABAQUS Process Automation Portal menu The portal provides examples of plug ins and customized applications as well as RU
108. er and has been modified to run on a Windows system ABA PATH ABA_HOME ABA_HOME cae PYTHONPATH ABA_HOME cae Python Lib ABA_HOME cae Python 0bj SABA _HOME cae exec lbr d boltApp1 sPYTHONPATHS ABA_LIBRARY_PATH ABA_HOME cae ABA_ SELECT ABA_HOME cae exec lbr ABA_HOME cae Python Obj lbr ABA_HOME cae External Acis ABA_HOME cae External ABA_HOME cae External ebt ABA_HOME exec Use the following syntax to start your application abaqus applicationName 11 5 COMMON METHODS 12 The application object This section describes the ABAQUS application object The application object manages the message queue timers chores GUI updating and other system facilities The following topics are covered e The application object Section 12 1 e Common methods Section 12 2 12 1 The application object The application object manages the message queue timers chores GUI updating and other system facilities Each application will have an application object which you typically create in the application s startup file For more information see Startup script Section 11 2 The constructor for the application object takes the following arguments AFXApp appName vendorName productName majorNumber minorNumber updateNumber prerelease The application and vendor names are intended to be keys into the registry The registry is a place to store settings that are persistent between sessions o
109. er can select zero or one items LIST_BROWSESELECT One item is always selected LIST_MULTIPLESELECT The user can select zero or more items LIST_EXTENDEDSELECT The user can select zero or more items drag shift and control selections are allowed When you are using a list that supports the selection of a single text item you can connect the list to an AFXStringTarget or to an AFXStringKeyword When you are using a list that supports the selection of more than one text item you can connect the list to an AFXTupleKeyword of type AFXTUPLE_ TYPE STRING The AFXDialog base class has special code designed to handle double click messages from a list If the user double clicks in a list the dialog box first attempts to call the Apply button message handler If LISTS AND COMBO BOXES the Apply button message handler is not found the dialog attempts to call the Continue button message handler If the Continue button message handler is not found the dialog attempts to call the OK button message handler As a result you do not need to do anything in your script to get this behavior However if you have special double click processing needs you can turn off this double click behavior by specifying AFXLIST NO AUTOCOMMIT as one of the list s option flags If you turn off the double click behavior you must catch the SEL DOUBLECLICKED message from the list in your dialog box and handle it appropriately Note Because the list may be used in c
110. er is allowed to pick only one entity the procedure will automatically advance to the next step after the user picks an entity however the user can back up to the previous step to change the 7 15 PICKING IN PROCEDURE MODES selection If the user is allowed to pick one or more entities the user must commit the selections by clicking mouse button 2 or by clicking the Done button on the prompt line The highlight level controls the color of the selected entities In some procedures different colors are used between steps to distinguish the selections The sequence style controls how a sequence of picked objects is represented in the command string If the sequence style is ARRAY the picked objects will be represented as the concatenation of slices of arrays for example v 3 4 v 5 8 where v is a vertex array If the sequence style is TUPLE the picked objects will be represented as a tuple of individual objects for example v 3 v 5 v 6 v 7 The style you choose depends on the format accepted by the command that you intend to issue Some commands in ABAQUS CAE accept both styles but some accept only one or the other For further details on the arguments to the AFXPickStep constructor see the ABAQUS GUI Toolkit Reference Manual 7 5 2 Refining what the user can select A refinement qualifies the types of pickable entities specified in the AFXPickStep constructor The following example shows how to select only straight edges
111. es Section 14 2 2 e Constructing the base class Section 14 2 3 e Registering persistent toolsets Section 14 2 4 e Registering modules Section 14 2 5 THE ABAQUS CAE MAIN WINDOW 14 2 1 Main window example To create a main window for a particular application you start by deriving a new class from the AFXMainWindow class In the constructor of the main window you register the modules and toolsets used by your application The following script constructs the ABAQUS CAE main window The script is described in detail in the following sections Details of how you construct modules and toolsets are given in Chapter 8 Creating a GUI module and Chapter 9 Creating a GUI toolset from from from from from abaqusGui import sessionGui import canvasGui import CanvasToolsetGui viewManipGui import ViewManipToolsetGui appIcons import appIconData appMinilconData FE HEHE HE E HE E HE HE HE HE HE HE HE HE HE HE HE HE HE HE FE HE HE HE FE HE FE HE FE HE FE HE FE HE FE HE FE HE FE HE FE EEE AEE HERES HEE HE Class definition FEAE HE HE HE FE FE FE HE HE E FE FE FE HE HE E FE FE FE FE E E FE FE FE FE HE E FE FE FE FE HE AE FE FE FE FE FE E AE FE FE FE FE HE AE E FE FE FE HE HE HE HE EHE HE HE class CaeMainWindow AFXMainWindow H w w w w w a m m a m a a m m a y a a m m a a ay ay m m a a ay ay a m m a ay ay ay m m a y y y m m e N y N ma Aa e a def _ init _ self app windowTitle Construct
112. es the Show dotted lines in hidden render style button DATA DIALOG BOXES e Stipples the Show edges in shaded render style button e Checks the Show silhouette edges button These transitions can be described as follows e If the value of the render style keyword equals WIREFRAME send the Show dotted lines button an ID_ DISABLE message e Ifthe value of the render style keyword equals WIREFRAME send the Show edges in shaded button an ID_ DISABLE message e Ifthe value of the render style keyword equals WIREFRAME send the Show silhouette edges button an ID ENABLE message You can write these transitions with the ABAQUS GUI Toolkit as follows self addTransition form renderStyleKw AFXTransition EQ WIREFRAME getId showDottedBtn MKUINT FXWindow ID DISABLE SEL_COMMAND None self addTransition form renderStyleKw AFXTransition EQ WIREFRAME getId showEdgesBtn MKUINT FXWindow ID DISABLE SEL COMMAND None self addTransition form renderStyleKw AFXTransition EQ WIREFRAME getId showSilhouetteBtn MKUINT FXWindow ID ENABLE SEL COMMAND None You can also pass additional user data to the object using the last argument of the addTransition method Figure 5 8 shows an example that uses transitions to control how the application stipples widgets 5 6 6 Updating your GUI If the GUI behavior of your dialog box cannot be described in terms of simple transitions for example if you need to stipple a button b
113. essage The selector is made up of the message ID and the message type You can use the MKUINT function to create a selector for example MKUINT ID_1 SEL COMMAND The user data must be None since this feature is not supported in the ABAQUS GUI Toolkit 6 4 5 Automatic GUI updating GUI updating is initiated automatically by the ABAQUS GUI Toolkit when there are no more events to be handled usually when the GUI is idle and waiting for some user interaction During the automatic GUI update process each widget sends a SEL_UPDATE message to its target asking to be updated In this way the GUI is constantly polling the application state to keep itself up to date For example during automatic GUI updating a check button sends an update message to its target The target checks some application state and determines whether or not the check button should be checked If the button should be checked the target sends back an ID_ CHECK message otherwise it sends an ID UNCHECK message Widgets in the toolkit are bi directional that is they can be in either a push state or a pull state push state In a push state the widgets are collecting and sending user input to the application When a widget is in the push state it does not participate in the automatic GUI updating process Because the widget is not participating in the automatic GUI updating process the user has control over the input rather than the GUI attempting to update the widget pull
114. etGui class MyVisModuleGui VisualizationGui def _ init self Construct the base class VisualizationGui init self Register my toolset self registerToolset MyToolsetGui GUI_IN MENUBAR GUI_IN_ TOOLBOX MyVisModuleGui File myMainWindow py from abaqusGui import class MyMainWindow AFXMainWindow def _init self app windowTitle self registerModule Visualization myVisModuleGui If you derive a toolset from an ABAQUS CAE toolset you must construct that toolset using the makeCustomToolsets method of AFXMainWindow You must use themakeCustomToolsets method to insure that the toolset is created at the appropriate time during application startup This will avoid any conflicts with ABAQUS CAE modules that also make use of the module For example if you derive a new toolset from the Datum toolset you must create the new toolset in makeCustomToolsets This approach is illustrated in the following example The new toolset will also appear in the Part module in place of the standard Datum toolset 10 3 THE HELP TOOLSET In your main window file class MyMainWindow AFXMainWindow def _init self app windowTitle def makeCustomToolsets self from myDtmToolsetGui import MyDtmGui Store the toolset as a member of the main window if you want to register it in one of your modules too self myDtmGui MyDtmGui In your module GUI file class MyModuleGui AFXModuleGui
115. f the application for example the size and location of the application on the desktop when the application it starts The registry is currently not used by ABAQUS but these keys are included as placeholders for future capabilities The registry will have various sections that allow you to group settings Some settings may apply to all products from a particular vendor and some settings may apply to only a specific product from a vendor By default ABAQUS displays the product name and version numbers in the main window s title bar for more information see The title bar Section 13 2 12 2 Common methods You can access the application object using the following statement app getAFXApp The following list shows some of the most commonly used application methods getAFXMainWindow Returns a handle to the main window object getProductName Returns the product name COMMON METHODS getVersionNumbers Returns a tuple of majorNumber minorNumber updateNumber getPrerelease Returns TRUE if this application is a prerelease beep Rings the system bell 12 2 AN OVERVIEW OF THE MAIN WINDOW 13 The main window This section describes the layout components and behavior of the ABAQUS main window The following topics are covered e An overview of the main window Section 13 1 e The title bar Section 13 2 e The menu bar Section 13 3 e The toolbar Section 13 4 e
116. following statement creates a dialog box that can be occluded by any other windows in the application AFXDialog app title actionButtonIds 0 w opts DIALOG NORMAL x 0 y 0 w 0 h 0 5 5 3 Sizing and location By default the user cannot resize a dialog box However if a dialog box contains text fields or lists that can be stretched to show more entries the user should be allowed to resize the dialog box Resizing can be allowed by specifying the DECOR_RESIZE flag in the dialog box constructor Note Dialog boxes created by AFXDialog do not support minimizing and maximizing they ignore these flags if they are included in the dialog box constructor You should never specify the size and location of the dialog box in its constructor The ABAQUS GUI Toolkit will place the dialog box on the screen and determine its proper size CUSTOM DIALOG BOXES 5 5 4 Action area The action area of a dialog box contains buttons such as OK and Cancel These buttons allow the user to commit values from the dialog box to close the dialog box or to perform some other action AFXDialog supports the automatic creation of an action area and its buttons through the use of bit flags in the dialog box constructor You can use the flags described in Table 5 1 to include standard action area buttons Table 5 1 Action area flags Button flag Message ID Label Semantics AFXDialog AFXDialog OK Commit the values in the dialog OK ID_CLICKED_OK b
117. formation please see the ABAQUS Home Page or contact your local ABAQUS support office Training All ABAQUS offices offer regularly scheduled public training classes The Introduction to ABAQUS seminar covers basic modeling using ABAQUS CAE and linear and nonlinear applications such as large deformation plasticity contact and dynamics using ABAQUS Standard and ABAQUS Explicit Workshops provide as much practical experience with ABAQUS as possible Advanced seminars cover topics of interest to customers with experience using ABAQUS such as engine analysis metal forming fracture mechanics and heat transfer We also provide training seminars at customer sites On site training seminars can be one or more days in duration depending on customer requirements The training topics can include a combination of material from our introductory and advanced seminars Workshops allow customers to exercise ABAQUS on their own computers For a schedule of seminars see the ABAQUS Home Page or call ABAQUS Inc or your local ABAQUS representative Documentation The following documentation and publications are available from ABAQUS unless otherwise specified in printed form and through the ABAQUS online documentation For more information on accessing the online books refer to the discussion of execution procedures in the ABAQUS Analysis User s Manual Modeling and Visualization e ABAQUS CAE User s Manual This reference document for A
118. g Sun Mills 166 Valley Street Providence RI 02909 2499 Tel 1 401 276 4400 Fax 1 401 276 4408 E mail support Abaqus com http www abaqus com Sales Support UNITED STATES ABAQUS Central Inc 1440 Innovation Place West Lafayette IN 47906 1000 Tel 1 765 497 1373 Fax 1 765 497 4444 E mail support AbaqusCentral com ABAQUS Erie Inc 3601 Green Road Suite 316 Beachwood OH 44122 Tel 1 216 378 1070 Fax 1 216 378 1072 E mail support AbaqusErie com ABAQUS South Inc 3700 Forums Drive Suite 101 Flower Mound TX 75028 Tel 1 214 513 1600 Fax 1 214 513 1700 E mail support AbaqusSouth com ARGENTINA KB Engineering S R L Florida 274 Oficina 35 1005 Buenos Aires Argentina Tel 54 11 4326 9176 7542 Fax 54 11 4326 2424 E mail sanchezsarmiento arnet com ar ABAQUS Europe BV Gaetano Martinolaan 95 P O Box 1637 6201 BP Maastricht The Netherlands Tel 31 43 356 6906 Fax 31 43 356 6908 E mail info europe abaqus com and Services ABAQUS East LLC 300 Centerville Road Suite 209W Warwick RI 02886 0201 Tel 1 401 739 3637 Fax 1 401 739 3302 E mail support AbaqusEast com ABAQUS Great Lakes Inc 14500 Sheldon Road Suite 160 Plymouth MI 48170 2408 Tel 1 734 451 0217 Fax 1 734 451 0458 E mail support AbaqusGreatLakes com ABAQUS West Inc 39221 Paseo Padre Parkway Suite F Fremont CA 94538 1611 Tel 1 510 794 5891 Fax 1 510 794
119. g a customized application This part describes how you create a customized application The following topics are covered e Chapter 11 Creating an application e Chapter 12 The application object e Chapter 13 The main window e Chapter 14 Customizing the main window STARTUP SCRIPT 11 Creating an application This chapter explains how to create an application The following topics are covered e Design overview Section 11 1 e Startup script Section 11 2 e Licensing and command line options Section 11 3 e Installation Section 11 4 11 1 Design overview An application consists of the two fundamental pieces e Kernel code e GUI code The kernel code consists of Python modules that contain functions and classes for performing various tasks for example creating parts or postprocessing results The GUI code provides a convenient user friendly mechanism for gathering the inputs required for the kernel code Kernel coding is described in the ABAQUS Scripting User s Manual and the ABAQUS Scripting Command Reference Manual To develop the GUI code you begin with a startup script that launches the application from the command line The script creates an application object which interacts with the window manager and controls a main window The main window provides components such as a menu bar a toolbar and a toolbox From that core you add functionality to the application by registeri
120. he application takes when each of these buttons is clicked Table 5 2 Action area buttons Button Action OK Send the form an ID_COMMIT SEL_COMMAND message and its button ID Apply Send the form an ID_COMMIT SEL_COMMAND message and its button ID Continue Send the form an ID_GET_NEXT SEL_ COMMAND message Defaults Send the form an ID_SET_DEFAULTS SEL_COMMAND message Cancel Check for bailout send the form an ID_DEACTIVATE SEL_COMMAND message x in title bar Perform the Cancel button action 5 7 Common dialog boxes The ABAQUS GUI Toolkit provides some pre built dialog boxes for handling common operations This section provides details on how to use these dialog boxes The following topics are covered e File Directory selector Section 5 7 1 e Print dialog box Section 5 7 2 e Color selector dialog box Section 5 7 3 5 7 1 File Directory selector The File Selector dialog box is used to gather a file or directory name from the user It has the following characteristics e The title bar can be set e The file filters can be set e The following error checking is provided Check to see if the file exists Check for proper permissions Check to see if the selection is a file COMMON DIALOG BOXES e Allows read only access e Accepts keywords and a target The file selection dialog box has the following prototypes AFXFileSelectorDialog form title fileNameKw re
121. i ABAQUS Engineering India Pvt Ltd 3M Prince Arcade 22 A Cathedral Road Chennai 600 086 Tel 91 44 28114624 Fax 91 44 28115087 E mail abaqus abaqus co in JAPAN Tokyo ABAQUS Inc 3rd Floor Akasaka Nihon Building 5 24 Akasaka 9 chome Minato ku Tokyo 107 0052 Tel 81 3 5474 5817 Fax 81 3 5474 5818 E mail tokyo abaqus jp JAPAN Osaka ABAQUS Inc 9th Floor Higobashi Watanabe Building 6 10 Edobori 1 chome Nishi ku Osaka 550 0002 Tel 81 6 4803 5020 Fax 81 6 4803 5021 E mail osaka abaqus jp MALAYSIA Worley Advanced Analysis 19th Floor Empire Tower City Square Centre 182 Jalan Tun Razak 50400 Kuala Lumpur Tel 60 3 2161 2266 Fax 60 3 2161 4266 E mail abaqus my worley com au POLAND BudSoft Sp z 0 0 61 807 Poznan Sw Marcin 58 64 Tel 48 61 8508 466 Fax 48 61 8508 467 E mail budsoft budsoft com pl SINGAPORE Worley Advanced Analysis 491B River Valley Road 09 01 Valley Point Singapore 248373 Tel 65 6735 8444 Fax 65 6735 7444 E mail abaqus sg worley com au KOREA ABAQUS Korea Inc Suite 306 Sambo Building 13 2 Yoido Dong Youngdeungpo ku Seoul 150 010 Tel 82 2 785 6707 Fax 82 2 785 6709 E mail info abaqus co kr NEW ZEALAND Matrix Applied Computing Ltd P O Box 56 316 Auckland Courier Unit 2 5 72 Dominion Road Mt Eden Auckland Tel 64 9 623 1223 Fax 64 9 623 1134 E mail abaqus tech matrix co
122. ich the keywords are used For example if you have two pick steps you must create the keyword passed into the first pick step before you create the second keyword which is passed into the second pick step Creating the keywords associated with pick steps in the same order as the pick steps in which the keywords are used ensures that the necessary setup commands are issued in the proper order for the command to work correctly You can specify many parameters when picking items from the viewport You specify some of these parameters in the AFXPickStep constructor and you specify other parameters by calling various methods of the pick step To construct a pick step you must at least supply the following e A procedure e An object keyword e A prompt for the prompt line e A bit flag or flags specifying which type of entities may be picked The following example shows how you can write a pick step class MyProcedure AFXProcedure def _ init__ self owner AFXProcedure init self owner self cmd AFXGuiCommand self myMethod myObject self nodeKw AFXObjectKeyword self cmd node TRUE def getFirstStep self return AFXPickStep self self nodeKw Select a node NODES Optional parameters in the constructor allow you to specify the following e Whether the user should pick one entity or one or more entities ONE the default or MANY e The highlight level 1 4 e The sequence style ARRAY the default or TUPLE If the us
123. ing a GUI module To create a new GUI module you must follow these steps Derive a new class from a module base class Create menus in the menu bar Create icons in the toolbar This step is optional Create icons in the toolbox This step is optional Create modes to collect input from the user and issue commands Modes include procedures and dialog boxes Create methods to handle any special behavior not handled by the module s modes This step is optional These steps are descibed in detail in the following sections 8 2 GUI module example The AFXModuleGui base class provides various module infrastructure support functions For example the AFXModuleGui base class keeps track of the module s menus along with its toolbar and toolbox icons As a result the menus toolbars and icons can be swapped in and out automatically as the user changes modules The following example shows how to create a main window subsequent sections explain the details of this example 8 1 GUI MODULE EXAMPLE from abaqusGui import from myModes import mode_1 mode _2 mode 3 from myIcons import from myToolsetGui import MyToolsetGui class MyModuleGui AFXModuleGui Iinnnnnnanannnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn def _ init self Construct the base class AFXModuleGui init self moduleName My Module displayTypes PART Menu items menu AFXMenuPane self AFXMenuTitle self amp Menul
124. ion see Keeping the GUI and commands up to date Section 6 4 3 If there is no kernel object associated with your command for example when creating a new object you can set the keyword values by specifying a default value in the constructor If you have a default object that you want to use to reestablish default values for the dialog box you can use the mode s registerDefaultsObject method to register an object whose values will be queried when the user presses the Defaults button in the dialog box For more information see Defaults objects Section 6 4 15 By default dialog boxes are posted as modeless or nonmodal You can change the behavior by calling setModal TRUE to have a dialog box posted as modal In most cases you set the behavior only once however you can change the behavior as often as needed by calling the setModal method in the getFirstDialog or getNextDialog methods For more information see Modal versus modeless Section 5 2 7 3 3 getFirstDialog You must write the getFirstDialog method for your mode The getFirstDialog method should return the first dialog box of the mode In Form example Section 7 3 1 a pointer to the form is passed into the dialog box constructor The dialog box will use this pointer to access the mode s keywords If you want the same default values to appear every time you post the dialog box you must call the setKeywordValuesToDefaults method before returning the dia
125. ion viewports s TRUE 6 4 4 Targets and messages The ABAQUS GUI Toolkit employs a target message system to achieve communication within the GUI process The target message system is in contrast to for example Motif s callback mechanism All widgets can send and receive messages from any other widget A message consists of two components e A message type e A message ID The message type indicates what kind of event occurred for example clicking a button The message ID identifies the sender of the message Most widgets in the ABAQUS GUI Toolkit take arguments that specify their target and their ID Even if a widget does not take a target and ID as arguments you can set these attributes using the setTarget and setSelector methods For example FXButton parent Label tgt self sel self ID_1 groupBox FXGroupBox parent groupBox setTarget self groupBox setSelector self ID_2 Widgets are capable of sending several types of messages Two ofthe most common message types are SEL COMMAND and SEL_UPDATE The SEL COMMAND message type generally indicates that a widget was committed for example the user clicked a push button The SEL_UPDATE message is sent when a widget is requesting its target to update its state for more information see Automatic GUI updating Section 6 4 5 A message is routed to a message handler using a map defined in the target class You add an entry in the map by specifying which method to
126. ition please give the receptionist the support engineer s name if contacting us via telephone or include it at the top of any e mail correspondence Systems support ABAQUS systems support engineers can help you resolve issues related to the installation and running of ABAQUS including licensing difficulties that are not covered by technical engineering support You should install ABAQUS by carefully following the instructions in the ABAQUS Installation and Licensing Guide If you are able to complete the installation please make sure that the product verification procedure was run successfully at the end of the installation procedure Successful verification for licensed products would indicate that you can run these products on your computer unsuccessful verification for licensed products indicates problems with the installation or licensing or both If you encounter problems with the installation licensing or verification first review the instructions in the ABAQUS Installation and Licensing Guide to ensure that they have been followed correctly If this does not resolve the problems consult the ABAQUS Answers database in the ABAQUS Online Support System for information about known installation problems If this does not address your situation please create an incident in the AOSS and describe your problem including the output from abaqus info support If you call mail e mail or fax us about a problem instead of using the AOSS pleas
127. lbar getAFXApp getAFXMainWindow getToolbar getWidgetFromText toolbar New Model nDatabase hide getWidgetFromText toolbar Save Model nDatabase hide Add an item to the File menu just above Exit btn AFXMenuCommand self menu Custom Button None MyForm self AFXMode ID_ACTIVATE sep getSeparator menu 6 btn linkBefore sep Rename the File menu fileMenu getWidgetFromText menubar File fileMenu setText MyFile Change a toolbar button icon btn getWidgetFromText toolbar Open icon FXXPMIcon getAFXApp boltToolboxIconData btn setIcon icon 10 7 AN EXAMPLE OF CUSTOMIZING A TOOLSET This example script illustrates the following Deriving a new toolset class To modify a toolset GUI you begin by deriving a new class from it Inside the new class constructor body you must call the base class constructor and pass self as the first argument Removing items from a menu or toolbar You can remove items from a menu by hiding them You use the getWidgetFromText or the getSeparator functions to obtain the widgets and call the hide method to remove them Adding items to a menu You can insert items into an existing menu by creating new menu commands and positioning them using the linkBefore or linkAfter methods Renaming items and changing icons You can change the text or icon associated with a widget by calling the setText or setIcon methods 10 8 Part VI Creatin
128. le of customizing a toolset PART VI CREATING A CUSTOMIZED APPLICATION Creating an application Design overview Startup script Licensing and command line options Installation The application object The application object Common methods The main window An overview of the main window The title bar The menu bar The toolbar The context bar CONTENTS 8 1 8 2 8 3 8 4 9 1 9 3 9 4 10 1 10 2 10 3 11 1 11 2 11 3 11 4 12 1 12 2 13 1 13 2 13 3 13 4 13 5 CONTENTS The module toolbox 13 6 The drawing area and canvas 13 7 The prompt area 13 8 The message area 13 9 The command line interface 13 10 14 Customizing the main window Modules and toolsets 14 1 The ABAQUS CAE main window 14 2 A Icons B Colors and RGB values Part Overview This part provides an overview of the ABAQUS GUI Toolkit and how you use the toolkit to create a customized application This part also describes the layout of this manual The following topic is covered e Chapter 1 Introduction WHAT CAN DO WITH THE ABAQUS GUI Toolkit Introduction 1 1 This chapter provides an overview of the ABAQUS GUI Toolkit The ABAQUS GUI Toolkit is one of the ABAQUS Process Automation tools that allow you to modify and extend the capabilities of ABAQUS CAE to enable a wide range of users to generate more efficient ABAQUS solutions The following topics are covered e What can I do with the ABAQUS GUI Toolkit
129. lems are included in this manual Training Getting Started with ABAQUS This document is a self paced tutorial designed to help new users become familiar with using ABAQUS CAE to create solid shell and framework models and ABAQUS Standard or ABAQUS Explicit to perform static quasi static and dynamic stress analysis simulations It contains a number of fully worked examples that provide practical guidelines for performing structural analyses with ABAQUS In addition three comprehensive tutorials are provided to introduce users familiar with the ABAQUS solver products to the ABAQUS CAE interface e Getting Started with ABAQUS Standard Keywords Version This online only document is designed to help new users become familiar with the ABAQUS Standard input file syntax for static and dynamic stress analysis simulations The ABAQUS Standard keyword interface is used to model examples similar to those included in Getting Started with ABAQUS e Getting Started with ABAQUS Explicit Keywords Version This online only document is designed to help new users become familiar with the ABAQUS Explicit input file syntax for quasi static and dynamic stress analysis simulations The ABAQUS Explicit keyword interface is used to model examples similar to those included in Getting Started with ABAQUS e Lecture Notes These notes are available on many topics to which ABAQUS is applied They are used in the technical seminars that ABAQUS Inc presents to help
130. lity to the application by deriving from the main window base class and then registering modules and toolsets The following topics are covered e Modules and toolsets Section 14 1 e The ABAQUS CAE main window Section 14 2 14 1 Modules and toolsets Modules are one of the fundamental concepts of an interactive ABAQUS application A module serves to group functionality into logical units for example a unit that creates parts or a unit that meshes the assembly An interactive ABAQUS application presents only one module at a time to the user Presenting only one module makes the interface less complicated because the interface shows fewer GUI controls and allows the user to focus on one major task at a time ABAQUS is designed to manipulate modules by swapping in one module s GUI while swapping out the previous module s GUI when requested by the user Toolsets are similar to modules in that they group functionality into logical units However toolsets generally contain less functionality than modules because toolsets focus on one particular task for example partitioning Toolsets can be used in more than one module 14 2 The ABAQUS CAE main window This section describes how you can create an application by deriving a new class from the AFXMainWindow class and registering the modules and toolsets used by your application The following topics are covered e Main window example Section 14 2 1 e Importing modul
131. lly not recommended that you modify ABAQUS CAE modules and toolsets because future changes to ABAQUS CAE may break your application However if you do have a need to modify some of the ABAQUS CAE modules or toolsets you can make changes by deriving a new class from one of them and then adding or removing components To derive a new class you must know the appropriate class name and you must call that class s constructor in your constructor The table below lists the class names and registered names for all the ABAQUS CAE modules that are available in the ABAQUS GUI Toolkit You can import these class names from abaqusGui When you register a module derived from one of the ABAQUS CAE modules you must use the name shown in the table for the displayedName argument in the main window s registerModule method If you do not use the name shown some GUI infrastructure components may not function correctly Class name Name PartGui Part PropertyGui Property AssemblyGui Assembly StepGui Step InteractionGui Interaction LoadGui Load ABAQUS CAE GUI MODULES AND TOOLSETS Class name Name MeshGui Mesh JobGui Job VisualizationGui Visualization SketchGui Sketch When you register a toolset you must specify in the registerToolset method in which locations the menu bar the toolbar or the toolbox the toolset creates the widget If you omit a toolse
132. lly by posting an error dialog box ABAQUS CAE uses an IPC protocol to achieve communication between the kernel and GUI processes For example the GUI often needs to query the kernel for a list of existing part names or for the values of a particular load that is about to be edited from a dialog box Similarly the GUI may need to be notified when some kernel value changes so that the GUI can update itself for example to post new job messages in the Job Monitor dialog box ABAQUS CAE uses targets and messages and the GUI updating process built into the ABAQUS GUI Toolkit to achieve communication within the GUI process For example an options dialog box may need to update when the current viewport is changed or some widgets in a dialog box may need to be grayed out when the user clicks a particular button Figure 6 1 illustrates the communication between the kernel and the GUI processes when the user clicks on a button and then enters values in the dialog box that appears Figure 6 1 Kernel Process GUI Process User clicks button that will post a dialog bot Query is processed l Values are sent to GUI Command is executed 1 Kernel is queried for values Values are set dialog bot is posted 1 User changes values in dialog bot i GUI responds to user s changes if necessary e g stipples widgets 1 l D
133. log Ss y y Get user input 4 N v doCustomChecks verifyCurrentKeywordValues N lt 7 lt getCommandString doCustomChecks sendCommandString handleException lt P lt getNextStep Dialog N doCustomTasks Y N deactivate or Loop Figure 7 1 The mode processing sequence verifyCurrentKeywordValues The verifyKeywordValues method calls the verify method for each keyword associated with the current step or dialog box and the method posts an error dialog box if necessary The verifyCurrentKeywordValues method returns TRUE if no errors were encountered otherwise it returns FALSE and terminates further processing MODE PROCESSING doCustomChecks The doCustomChecks method has an empty implementation in the base class You can redefine this method to perform any additional checking of keyword values typically to perform range checking or to check some interdependency between values The doCustomChecks method should return TRUE if no errors were encountered otherwise it returns FALSE so that further command processing will be terminated The doCustomChecks method is called by the mode during step and dialog box processing and during command processing 7 2 4 Command processing When the mode finishes collecting inputs from the user it calls a series of methods If neede
134. log box Similarly if the user is picking a single entity the drag shape and drag scope buttons are not available As a result procedures generally do not need to set the available selection options explicitly If you need to set these options you can use the procedure s setSelectionOptions method You must set the procedure selection options prior to creating the first pick step For more information see the ABAQUS GUI Toolkit Reference Manual Normally a procedure will set these options only at the start of the procedure However during the procedure the user may change the settings and the modified settings will be retained from step to step during the rest of the procedure 7 5 6 Allowing the user to type in points If you want to allow the user to type in the coordinates of a point as an alternative to picking in the viewport you can call the addPointKeyIn method and pass it a tuple keyword The addPointKeyIn method posts a text field on the prompt line The type of the keyword passed into the addPointKeyIn method determines what values are collected from the user for example two or three values and whether those values are float or integer types For example in the constructor of your procedure you could define an additional keyword as shown in the following code self pointKwl AFXObjectKeyword self cmd point TRUE self pointKw2 AFXTupleKeyword self cmd point TRUE 3 3 AFXTUPLE_TYPE_FLOAT In one of the steps of your
135. log box as shown in Form example Section 7 3 1 7 8 FORM MODES 7 3 4 getNextDialog If your mode contains more than one dialog box you must write the getNextDialog method in addition to the getFirstDialog method The previous dialog box is passed into the getNextDialog method so that you can determine where the user is in the sequence of dialog boxes and act accordingly The getNextDialog method should return the next dialog box in the sequence or it should return None to indicate that it has finished collecting input from the user The following example is a modified version of the example in getFirstDialog Section 7 3 3 that illustrates how inputs are collected from the user in a series of three dialog boxes rather than just one def getFirstDialog self self dialogl PlateDBl self return self dialogl def getNextDialog self previousDb if previousDb self dialogl self dialog2 PlateDB2 self return self dialog2 elif previousDb self dialog2 self dialog3 PlateDB3 self return self dialog3 else return None 7 3 5 Collecting input from the GUI To collect input from the user via the GUI the keywords defined in the mode must be connected to widgets in the dialog box The AFXDataDialog class takes a mode argument in its constructor Because the form stores keywords the dialog box can access these keywords and assign them to be targets of widgets in the dialog box As a result the GUI can u
136. lowing statement returns the second separator in the File menu separatorWidget getSeparator fileMenu 2 The following example shows how you can modify the File toolset GUI Figure 10 1 shows the File menu before and after the script is executed MyFile Model wWiewport Eile Model Viewpot y C a 7 Open Otrl O New Open Ctrl O Close ODB Mc Close ODB Mc import gt Save Otrl S Export gt O SaveAs Bun Script Import gt Macro Manager Export gt Custom Button Bun Script Print Ctrl P Macro Manager Exit Ctrl Q Print Ctrl P Exit Ctrl Q Figure 10 1 The toolbar and the File menu before and after executing the example script from sessionGui import FileToolsetGui from myIcons import boltToolboxIconData from myForm import MyForm class MyFileToolsetGui FileToolsetGui 10 6 AN EXAMPLE OF CUSTOMIZING A TOOLSET Innnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn def _ init self Construct the base class FileToolsetGui init self Remove unwanted items from the File menu including the second separator menubar getAFXApp getAFXMainWindow getMenubar menu getWidgetFromText menubar File getMenu getWidgetFromText menu New hide getWidgetFromText menu Save hide getWwidgetFromText menu Save As hide getSeparator menu 2 hide Remove unwanted items from the toolbar too
137. lt in a command argument that is a tuple of tuples The values in a table keyword can be Ints Floats or Strings The default minimum number of rows is 0 and the default maximum number rows is 1 indicating that the number of rows is unlimited Tables can vary in size because the user can add or delete rows as 6 17 GUI COMMANDS a result you usually specify the defaults for the minimum and maximum number of rows For example to generate a command that creates XY data you can define the following keywords in the form self cmd AFXGuiCommand self XYData session self nameKw AFXStringKeyword self cmd name TRUE self dataKw AFXTableKeyword self cmd data TRUE 0 1 AFXTABLE_TYPE_FLOAT In the dialog box you connect the table keyword to a table using a selector value of zero table AFXTable vf 6 3 6 3 form dataKw 0 AFXTABLE NORMAL AFXTABLE EDITABLE 6 4 14 Object keyword example The AFXObjectKeyword has a variable name for its value In most cases you use an AFXObjectKeyword in a command that is preceded by some setup commands For example p mdb models Model 1 parts Part 1 session viewports Viewport 1 setValues displayedObject p You also use an AFXObjectKeyword in procedures that require picking For more information see Picking in procedure modes Section 7 5 6 4 15 Defaults objects A defaults object can be used to restore the values of the keywords in a command to their
138. mands The ultimate goal of the GUI is to send a command to the kernel for execution therefore you should understand how kernel commands work Object oriented programming Python is an object oriented language and writing an application generally consists of deriving your own new classes writing methods for them and manipulating their data You should understand the concepts of object oriented programming GUI design Depending on the complexity of your application it may be helpful to have some training in user interface design and usability testing This will help you create an application that is both intuitive and easy to use ABAQUS offers training classes that cover Python kernel scripting and GUI design For more information contact your local sales office Training in GUI design is also available from a number of independent training organizations 1 3 ABAQUS GUI Toolkit basics The ABAQUS GUI Toolkit is an extension of the FOX GUI Toolkit just as the ABAQUS Scripting Interface is an extension of the Python programming language FOX which stands for Free Objects for X is a modern object oriented platform independent GUI toolkit Since the ABAQUS GUI Toolkit is ORGANIZATION OF THE ABAQUS GUI Toolkit USER S MANUAL platform independent once you write an application for one platform you can run that application on all supported platforms you do not need to change your source code The user interface produced by the AB
139. may ask you The support engineer will try to diagnose your problem from the model description and a description of the difficulties you are having The support engineer may need model sketches which can be sent via fax e mail or regular mail Plots of the final results or the results near the point that the analysis terminated may also be needed to understand what may have caused the problem If the support engineer cannot diagnose your problem from this information you may be asked to supply the input data The data can be attached to a support incident in the ABAQUS Online Support System It may also be sent by means of e mail tape disk or ftp Please check the ABAQUS Home Page http www abaqus com for the media formats that are currently accepted All support incidents are tracked in the ABAQUS Online Support System This enables you as well as the support engineer to monitor the progress of a particular problem and to check that we are resolving support issues efficiently To use the ABAQUS Online Support System you need to register with the system Visit the MY ABAQUS section of the ABAQUS Home Page for instructions on how to register If you are contacting us by means outside the AOSS to discuss an existing support problem and you know the incident number please mention it so that we can consult the database to see what the latest action has been and thus give you more efficient support as well as avoid duplication of effort In add
140. method 3 8 Widgets and fonts 3 9 4 Layout managers An overview of layout managers 4 1 Padding and spacing 4 2 Horizontal and vertical frames 4 3 Vertical alignment for composite children 4 4 vii CONTENTS General purpose layout managers 4 5 Row and column layout manager 4 6 Resizable regions 4 7 Rotating regions 4 8 Tab books 4 9 Layout hints 4 10 Layout examples 4 11 Tips for specifying layout hints 4 12 5 Dialog boxes An overview of dialog boxes 5 1 Modal versus modeless 5 2 Showing and hiding dialog boxes 5 3 Message dialog boxes 5 4 Custom dialog boxes 5 5 Data dialog boxes 5 6 Common dialog boxes 5 7 PART IV ISSUING COMMANDS 6 Commands An overview of commands 6 1 The kernel and GUI processes 6 2 Kernel commands 6 3 GUI commands 6 4 AF XTargets 6 5 Accessing kernel data from the GUI 6 6 Receiving notification of kernel data changes 6 7 7 Modes An overview of modes 7 1 Mode processing 7 2 Form modes 7 3 Procedure modes 7 4 Picking in procedure modes T3 viii PART V GUI MODULES AND TOOLSETS 8 Creating a GUI module An overview of creating a GUI module GUI module example Registering a GUI module Switching to a GUI module 9 Creating a GUI toolset 10 11 12 13 An overview of creating a GUI toolset GUI Toolset example Creating toolset components Registering toolsets Customizing an existing module or toolset ABAQUS CAE GUI modules and toolsets The Help toolset An examp
141. mode dimensionalityKw TWO_D PLANAR getId LAYOUT SIDE LEFT FXRadioButton gb Axisymmetric mode dimensionalityKw AXISYMMETRIC getId LAYOUT_SIDE_LEFT 6 4 12 Tuple keyword examples In the case of tuple keywords a value of zero for the message ID indicates that the entire tuple will be updated For example you can use a single text field to collect X Y and Z inputs from the user In this case the comma separated string entered by the user is used to set the entire value of the tuple keyword For example if you define a tuple keyword as follows self viewVectorKw AFXTupleKeyword cmd viewVector TRUE 3 3 you can connect the tuple keyword to a single text field as follows AFXTextField self 12 View Vector X Y Z mode viewVectorkw 0 AFXTEXTFIELD FLOAT Alternatively you can use three separate text fields to collect X Y and Z inputs Each of the text field widgets uses a message ID equal to the element number 1 based of the tuple to which they correspond For example 1 corresponds to the first element of the tuple 2 corresponds to the second element in the tuple etc In this case we can connect the keyword to three text fields as follows AFXTextField self 4 X mode viewVectorKw 1 AFXTextField self 4 Y mode viewVectorKw 2 AFXTextField self 4 Z mode viewVectorKw 3 6 4 13 Table keyword example The AFXTableKeyword must be connected to a table widget This type of keyword will resu
142. ms are displayed across the top of the main window under the menu bar and consist of a button that contains an icon Toolbar items are placed in a group that is shown only when its module or toolset is current The group also contains a separator that provides a visual distinction from the other groups of icons in the toolbar The example in GUI module example Section 8 2 creates a toolbar group and adds a button to the toolbar The new button invokes the same mode that will be invoked by the first menu item in the example For more information see Mode processing Section 7 2 8 2 4 Toolbox items Toolbox items are displayed along the left edge of the main window and consist of a button that contains an icon As with toolbar items toolbox items are placed in a group that is shown only when its module or toolset is current Similarly toolbox groups are spaced apart to provide a visual distinction from the other groups of icons in the toolbox The example in GUI module example Section 8 2 creates a toolbox group and adds a button to the toolbox The new button invokes the same mode as the first menu item in the example Toolboxes can also contain flyout menus When the user presses mouse button 1 on the flyout button and holds it down for a certain time span a flyout button displays a popup window containing buttons If the user just quickly clicks mouse button 1 on the flyout button the flyout popup is not displayed and the fl
143. n alternative way to provide help in your application is to use special methods that allow you to post a URL in a web browser For example from uti import webBrowser status status webBrowser displayURL http www abaqus com webBrowser openWithURL file D users someUser someFile html You can use any valid URL syntax such as http or file displayURL will display the URL ina currently open browser window if there are none it will open a new window openWithURL will always open a new browser window No exceptions are thrown but you can check the return status of these methods for success 10 5 AN EXAMPLE OF CUSTOMIZING A TOOLSET An example of customizing a toolset To modify an existing toolset you start by deriving a new class from it To modify widgets in the toolset you need to be able to access them The following functions in the ABAQUS GUI Toolkit allow you to access a widget e getWidgetFromText widget text The getWidgetFromText function returns a widget whose label or tip text matches the specified text and is also a child of the specified widget For example the following statement returns the widget that matches the Save As item in the File menu saveAsWidget getWidgetFromText fileMenu Save As getSeparator widget index The getSeparator function returns the n separator of the specified widget where n is specified by the one based index For example the fol
144. n the next section File Directory selector Section 5 7 1 includes an example that uses the showModal method 5 3 Showing and hiding dialog boxes Dialog boxes have show and hide methods that post or unpost the dialog box from the screen In most cases you do not need to call these methods because the mode infrastructure calls them for you However you may want to write your own show and hide methods to perform some special processing that will be executed just before your application posts or unposts the dialog box For example you can register and unregister queries inside the show and hide methods You must call the base class versions of the show and hide methods or the methods will not behave as expected For example in your dialog class code you could add the following lines def show self Do some special processing here Call base class method AFXDataDialog show self def hide self Do some special processing here Call base class method AFXDataDialog hide self MESSAGE DIALOG BOXES Message dialog boxes The AFXMessageDialog class extends the FXMessageDialog class by enforcing certain characteristics of the dialog box for example the window title and message symbol These characteristics make message dialog boxes in ABAQUS CAE consistent and easy to use This section describes the message dialog boxes that you can create with the ABAQUS GUI Toolkit The following topics are covered e Error dial
145. n window is what the user will see when the application is started The main window is discussed in more detail in Chapter 13 The main window The application constructor creates all the data structures needed for that object and the app create statement creates all the GUI windows required by the application object The app run statement displays the application and then enters an event loop The event loop then waits for user interaction 11 3 Licensing and command line options The startup script described in the previous section is run by specifying the name of the script as the argument to the custom option on the command line To start your application enter one of the following abaqus cae custom startupScript abaqus viewer custom startupScript where startupScript is the name of the startup script for your application and does not include a file extension You are responsible for making sure that the script exists in a directory specified in the PYTHONPATH environment variable defined in the abaqus aev file The abaqus aev file is described in Installation Section 11 4 The first argument to the abaqus command specifies the type of license to be checked out Specifying abaqus cae will check out a token named cae that will give you access to all the ABAQUS CAE kernel modules Specifiying abaqus viewer will check out a token called viewer that will give you access to only the visualization kernel module Therefore if yo
146. nd provides the following additional features e A bailout mechanism e Standard action area button behavior designed to work with a form e Keyword usage e Transitions that define GUI state changes in the dialog box 5 6 2 Constructor prototypes There are two prototypes of the AFXDataDialog constructor The difference between the two prototypes is the occluding behavior of the dialog box as illustrated in the following examples e The following statement creates a dialog box that always occludes the main window when overlapping with the main window AFXDataDialog mode title actionButtonIds 0 opts DIALOG NORMAL x 0 y 0 w 0 h 0 DATA DIALOG BOXES e The following statement creates a dialog box that always occludes its owner widget usually a dialog box when overlapping with the widget AFXDataDialog mode owner title actionButtonIds 0 opts DIALOG NORMAL x 0 y 0 w 0 h 0 When a dialog box is unposted it is removed from the screen By default a dialog box is deleted when it is unposted Deleting a dialog box removes both the GUI resources associated with the dialog box and the dialog box s data structures In contrast you can choose to destroy a dialog box when it is unposted Destroying a dialog box removes only the GUI resources and retains the dialog box s data structures If there is some dialog box GUI state that you want to retain between postings of the dialog box you should specify that the dial
147. nded and collapsed The FXTreeList constructor is defined by the following prototype FXTreeList p nvis tgt None sel 0 opts TREELIST NORMAL x 0 y 0 w 0 h 0 The arguments to the FXTreeList constructor are described in the following list parent The first argument in the constructor is the parent An FXTreeList does not draw a frame around itself therefore you may want to create an FXVerticalFrame to use as the parent of the tree You should zero out the padding in the frame so that the frame wraps tightly around the tree number of visible items The number of items that will be visible when the tree is first displayed target and selector You can specify a target and selector in the tree constructor arguments opts The option flags that you can specify in the tree constructor are shown in the following table Option flag Effect TREELIST_NORMAL default TREELIST_EXTENDEDSELECT TREELIST_EXTENDEDSELECT Extended selection mode allows the user to drag select ranges of items TREELIST_SINGLESELECT Single selection mode allows the user to select up to one item TREE WIDGETS Option flag Effect TREELIST_BROWSESELECT Browse selection mode enforces one single item to be selected at all times TREELIST_MULTIPLESELECT Multiple selection mode is used for selection of individual items TREELIST_AUTOSELECT Automatically select under cursor TREELIST_SHOWS_LINES Show lines between items TREELIST_SHOWS
148. ndler you can query the warning dialog box using the getPressedButtonId method The following examples illustrate how to create a warning dialog box You must define an ID in the form class from abaqusGui import class MyForm AFXForm ID_WARNING range AFXForm ID LAST AFXForm ID LAST 1 def _ init self owner Construct the base class AFXForm init self owner FXMAPFUNC self SEL COMMAND self ID_WARNING MyForm onCmdWarning def doCustomChecks self if lt someCondition gt showAFXWarningDialog self getCurrentDialog Save changes made in the dialog AFXdialog YES AFXDialog NO AFXDialog NO MESSAGE DIALOG BOXES self self ID_WARNING return FALSE return TRUE def onCmdWarning self sender sel ptr if sender getPressedButtonId AFXDialog ID_ CLICKED YES self issueCommands elif sender getPressedButtonId AFXDialog ID_ CLICKED NO self deactivate i Mold Designer x A Save changes made in the dialog ves No Cancel Figure 5 2 An example of a warning dialog box from showAFXWarningDialog 5 4 3 Information dialog boxes You post information dialog boxes to provide an explanatory message Information dialog boxes have the following characteristics e The application name is displayed in their title bar e An information symbol is displayed on the left side of the dialog box e The action area contains only a Dismiss button e They are mo
149. nel data from the GUI Section 6 6 e Receiving notification of kernel data changes Section 6 7 6 1 An overview of commands In ABAQUS CAE there are two types of commands kernel commands and GUI commands Kernel commands Kernel commands are used to build analyze and postprocess finite element models Kernel commands are documented in the ABAQUS Scripting Reference Manual GUI commands GUI commands are used by the user interface to process input gathered from the user and to construct a kernel command string that is sent to the kernel for execution GUI commands are documented in the ABAQUS GUI Toolkit Reference Manual 6 2 The kernel and GUI processes ABAQUS CAE executes in two processes a kernel process and a GUI process Kernel process The kernel process holds all the data and methods that ABAQUS CAE uses to perform modeling operations for example creating parts and meshing the assembly The kernel process can run independently of the GUI process 6 1 THE KERNEL AND GUI PROCESSES GUI process The GUI is a convenient way for the user to specify input to ABAQUS CAE A kernel command string is sent from the GUI process to the kernel process via the inter process communication IPC protocol The kernel process interprets and executes the kernel command string If the kernel command throws an exception the exception is propagated back to the GUI process where it should be caught and handled properly typica
150. ng procedure members and then checking the members during getNextStep as shown in the following example def getFirstStep self self plateWidthDB None 7 13 PICKING IN PROCEDURE MODES def self plateHeightDB None db PlateNameDB self self stepl AFXDialogStep self db return self stepl getNextStep self previousStep if previousStep self stepl if not self plateWidthDB self plateWidthDB PlateWidthDB self self step2 AFXDialogStep self self plateWidthDB return self step2 elif previousStep self step2 if not self plateHeightDB self plateHeightDB PlateHeightDB self self step3 AFXDialogStep self self plateHeightDB return self step3 else return None 7 5 Picking in procedure modes This section describes picking in procedure modes The following topics are covered e AFXPickStep Section 7 5 1 e Refining what the user can select Section 7 5 2 e Nonpickable entities Section 7 5 3 e Highlighting while selecting Section 7 5 4 e Selection options Section 7 5 5 e Allowing the user to type in points Section 7 5 6 e Picking by angle Section 7 5 7 e Limitations while selecting Section 7 5 8 7 14 PICKING IN PROCEDURE MODES 7 5 1 AFXPickStep The AFXPickStep class allows the user to pick entities in the current viewport You must create the keywords associated with pick steps in the same order as the pick steps in wh
151. ng modules and toolsets Modules and toolsets are a way of grouping functionality to be presented to the user For example the Part module in ABAQUS CAE groups all the functions related to creating and modifying parts ABAQUS CAE modules and toolsets can be included in your application and you can write your own modules and toolsets to provide custom functionality The widget library provides access to various GUI controls such as push buttons check buttons and text fields that are used to build dialog boxes These concepts are illustrated in Figure 11 1 Each of these steps is described in detail in subsequent sections 11 2 Startup script Every application is started from a short startup script The startup script performs the following tasks e Initializes an application object The application object is responsible for high level functions such as Managing message queues and timers and updating the GUI and controlling the main window It is not a visible object STARTUP SCRIPT Startup script Starts the application from the command line 1 Application object Interacts with window manager controls main window T Main window GUI Infrastructure main menus toolbar toolbox etc T GUI Modules Toolsets Functionality grouped by task e g Part module Datum toolset 1 Modes Responsible for gathering user input processing commands i Dialogs prompts User input mechanisms 1 Widgets GUI controls buttons text fields lists
152. ng statement contextBar getAFXApp getAFXMainWindow getContextBar 13 4 THE COMMAND LINE INTERFACE 13 6 The module toolbox The module toolbox contains icons for tools commonly used in the current module When you switch into a module that module s toolbox icons replace those of the previous module You can access the module toolbox using the following statement toolbox getAFXApp getAFXMainWindow getToolbox 13 7 The drawing area and canvas The canvas provides an infinite space upon which you can create and manipulate viewports The drawing area is a window into the visible part of the canvas You can access the canvas area using the following statement canvas getAFXApp getAFXMainWindow i_getCanvas The i_ in the method name indicates that this is an internal method that you should not normally use it is expected that only the GUI infrastructure needs to access this method 13 8 The prompt area The prompt area displays prompts to guide the user as well as work in progress WIP messages You can display messages in the prompt area during procedures For more information see Picking in procedure modes Section 7 5 13 9 The message area The application uses the message area to display informational and warning messages You can send messages to the message area using the following method mainWindow getAFXApp getAFXMainWindow mainWindow writeToMessageArea Wa
153. ng the base class The first statements in the CaeMainWindow class initialize the class by calling the base class constructor The mainWindow constructor takes a window title argument and two optional icon arguments a larger version of the icon and a smaller version of the icon The two icons are used in various places by the windowing system for example in the left corner of the window title bar Omit these arguments to use the standard ABAQUS CAE icons See Appendix A Icons for details on constructing icons 14 2 4 Registering persistent toolsets Toolsets that are registered with the main window as opposed to being registered with a module are available when the application first starts up In addition toolsets that are registered with the main window remain available throughout a session as the user switches modules To register a toolset you call the registerToolset method and pass in the toolset class You can register a help toolset with the application using the registerHelpToolset method A toolset 14 3 THE ABAQUS CAE MAIN WINDOW that is registered in this manner always appears to the right of all other menus in the menu bar For more information see Registering toolsets Section 8 2 5 Note Every application must register the viewManipGuiToolset 14 2 5 Registering modules Registering modules puts the module names into the Module combo box in the context bar However the module is not loaded and construct
154. ngle line complex numeric field from AFXTextField Toggled variation In many cases a check button precedes a labeled text field The check button allows the user to toggle the component on or off when the component is toggled off the text field becomes disabled The AFXTextField widget creates a check button with this behavior when you supply the AFXTEXTFIELD_CHECKBUTTON flag The following example creates a check button with a text field It also AFXTextField parent 8 AFXTextField None 0 AFXTEXTFIELD CHECKBUTTON AFXTEXTFIELD VERTICAL Integer AFXTextField Figure 3 12 An example of a check button with a labeled text field from AFXTextField TEXT WIDGETS Non editable variation In some cases you may want to change the behavior of a text field so that it cannot be edited by the user for example when a particular check button in the dialog box is not set In this case you can make the text field non editable when the check button is unset by calling the setEditable FALSE method of the AFXTextField widget Read only variation In some cases you may want to change the behavior of a text field so that it cannot be edited by the user and appears as a label making it clear that the user cannot change its contents For example when you are using the Load module in ABAQUS CAE there are some values that you can specify in the analysis step in which the load was created but you cannot change in subsequent steps The AFXTextField wi
155. nit self form FXMAPFUNC self SEL_RIGHTBUTTONPRESS self ID_TREE MyDB onCmdPopup FXMAPFUNC self SEL_COMMAND self ID TESTI MyDB onCmdTest1 FXMAPFUNC self SEL COMMAND self ID_TEST2 MyDB onCmdTest2 self menuPane None FXTreeList self 5 self self ID_TREE LAYOUT FILL X LAYOUT_ FILL Y TREELIST SHOWS BOXES TREELIST SHOWS _LINES TREELIST ROOT BOXES TREELIST_BROWSESELECT def onCmdPopup self sender sel ptr if not self menuPane self menuPane FXMenuPane self FXMenuCommand self menuPane Test1 None self self ID_TEST1 FXMenuCommand self menuPane Test2 None self LABELS AND BUTTONS self ID_TEST2 self menuPane create status x y buttons self getCursorPosition x y self translateCoordinatesTo self getRoot x y self menuPane popup None x y return 1 Note The AFXTable has its own popup menu commands that you should use in place of the approach described in this section 3 1 8 Toolbar and toolbox buttons The AFXToolButton widget displays no text in its button but the button generally has a tool tip You group the buttons created by AFXToolButton into toolbars using AFXToolbarGroups or into toolboxes using AFXToolboxGroups AFXToolbarGroups and AFXToolboxGroups provide visual grouping between buttons in the toolbar or toolbox For example Create toolbar icons group AFXToolbarGroup self AFXToolButton group tMy Module nToolbar Button icon s
156. og box is destroyed only when it is unposted Therefore when the dialog box is posted again it retains its data structures and the old state is still intact For example assume that your dialog box contains a table and the user resizes one of the columns of the table If you only destroy the dialog box when it is unposted the table column sizes will be remembered the next time the dialog box is posted To specify that a dialog box should be destroyed when unposted add the DIALOG_UNPOST_ DESTROY flag to the dialog box constructor s opts argument 5 6 3 Bailout AFXDataDialog supports automatic bailout handling through the specification of a bit flag in the dialog box constructor If you request bailout processing and the user changes some values in the dialog box and presses Cancel the application posts a standard warning dialog box The following statement requests bailout processing AFXDataDialog init__ self form Create Part self OK self CANCEL DIALOG ACTIONS_SEPARATOR DATADIALOG BAILOUT ii ABAQUS Beam x A Save changes made in the Fatigue Analysis dialog Figure 5 6 An example of a bailout After the standard warning dialog box has been posted the behavior is as follows e Ifthe user clicks Yes from the standard warning dialog box the data dialog box will be processed as if the user had originally pressed OK DATA DIALOG BOXES e Ifthe user clicks No from the standard warning dialog box the data dialog box will
157. og boxes Section 5 4 1 e Warning dialog boxes Section 5 4 2 e Information dialog boxes Section 5 4 3 e Specialized message dialog boxes Section 5 4 4 5 4 1 Error dialog boxes You post error dialog boxes in response to a failure condition that the application cannot resolve Error dialog boxes have the following characteristics e The application name is displayed in their title bar e An error symbol is displayed on the left side of the dialog box e The action area contains only a Dismiss button e They are modal For example mainWindow getAFXApp getAFXMainWindow showAFXErrorDialog mainWindow An invalid value was supplied im ABAQUS CAE x An invalid value was supplied Figure 5 1 An example of an error dialog box from showAFXErrorDialog MESSAGE DIALOG BOXES 5 4 2 Warning dialog boxes You post warning dialog boxes in response to a condition that the application needs user assistance to resolve Warning dialog boxes have the following characteristics e The application name is displayed in their title bar e A warning symbol is displayed on the left side of the dialog box e The action area may contain Yes No and Cancel buttons e They are modal To find out which button in the warning dialog box was pressed by the user you must pass the warning dialog box a target and a selector and you must create a message map entry in the form to handle that message In your message ha
158. ollect more input After all the inputs are collected from the user the mode verifies the input constructs the command and sends the command to the kernel If there is an exception thrown by the kernel the mode will handle the exception The mode processing sequence is shown in Figure 7 1 7 2 2 Activating a mode A mode is usually activated by sending it an ID ACTIVATE SEL COMMAND message This message causes the activate method of the mode to be called If you need to do any processing before a mode begins to collect input from the user you can redefine the activate method For example you can check that the current viewport contains a part before beginning a mode that requires the user to pick something on a part as shown in the following method def activate self vp session currentViewportName name session viewports vp displayedObject name modelName sessionState vp modelName if name in mdb models modelName parts keys AFXForm activate self else showAFXErrorDialog getAFXApp getAFXMainWindow A part must be displayed in the current viewport 7 2 3 Step and dialog box processing After a mode is activated it cycles through a sequence of events collecting inputs from the user and verifying the inputs After the user commits each step or dialog box the mode calls the following methods 7 2 MODE PROCESSING activate gt verifyKeywordValues v getFirstStep Dia
159. ombination with other types of widgets the list does not draw a border around itself As a result if you want a border around the list you must provide the border by placing the list inside some other widget such as a frame If you do not want a horizontal scrollbar use the HSCROLLING OFF flag this flag forces the list to size its width to fit its widest item The following is an example of a list within a vertical frame vf FXVerticalFrame parent FRAME THICK FRAME SUNKEN 0 0 0 0 0 O O 0 list AFXList vf 3 tgt sel LIST_BROWSESELECT HSCROLLING_OFF list appendItem Thin list appendItem Medium list appendItem Thick Thin Medium Thick Figure 3 14 An example of a list with a frame from AFXList 3 3 2 Combo boxes AFXComboBox provides a one of many selection from its items AFXComboBox combines a read only text field with a drop down list In addition AFXComboBox extends the functionality of the standard FXComboBox widget by providing a label and the ability to set and update its value based on the user data passed in with its items In most cases the user data are symbolic constant IDs After the parent argument the next three arguments to the AFXComboBox constructor are the width of the text field the number of visible list items when the list is exposed and the label If you specify the width as zero the combo box will automatically size itself to the widest item in its list For example comboBox AFXC
160. omboBox p 0 3 AFXComboBox comboBox appendItem Item 1 comboBox appendItem Item 2 RANGE WIDGETS comboBox appendItem Item 3 AFX ComboBox Iten 1 ixj Figure 3 15 An example of a combo box from AFXComboBox 3 3 3 List boxes The AFXListBox widget provides a one of many selection from its items AFXListBox differs from AFXComboBox in that the items displayed by AFXListBox can include icons AFXListBox extends the functionality of the standard FXListBox widget by providing an optional label and the ability to set and update its value based on the user data passed in with its items In most cases the user data are symbolic constant IDs For example listBox AFXListBox parent 8 3 AFXListBox keyword listBox appendItem Item 1 thinIcon listBox appendItem Item 2 mediumIcon listBox appendItem Item 3 thickIcon AFPXListBox Item 1 Figure 3 16 An example of a list box from AFXListBox 3 4 Range widgets This section describes the widgets in the ABAQUS GUI Toolkit that allow the user to specify a value within certain bounds The following topics are covered e Sliders Section 3 4 1 e Spinners Section 3 4 2 3 4 1 Sliders The AFXSlider widget provides a handle that the user can drag to set a value using only the mouse AFXSlider extends the capability of the FXSlider widget by providing the following e An optional title RANGE WIDGETS e Minimum and maximum range labels
161. on 3 2 Text widgets This section describes the widgets in the ABAQUS GUI Toolkit that allow the user to input text The following topics are covered e Single line text field widget Section 3 2 1 e Multi line text widget Section 3 2 2 3 2 1 Single line text field widget The AFXTextField widget provides a single line text entry field AFXTextField extends the capability of the standard FXTextField widget with the following 3 7 TEXT WIDGETS e An optional label e Support for a toggled version and a read only state e An additional numeric type complex e Horizontal and vertical layouts For example AFXTextField parent 8 String AFXTextField String AFXTextField f Figure 3 10 An example of a single line text field from AFXTextField Text fields are generally connected to keywords and the type of the keyword determines the type of input allowed in the text field For example if the text field is connected to an integer keyword the keyword will verify that the input in the text field is a valid integer You do not need to specifiy any option flags for the text field to get this behavior Complex text fields are an exception to this to display the extra field needed to collect complex input you must specify the bit flag shown in the following example AFXTextField parent 8 Complex AFXTextField None 0 AFXTEXTFIELD_COMPLEX Complex AF X TextField f f i Figure 3 11 An example of a si
162. on A 16 x 16 pixel used on Windows for the application in the title bar and system tray opts Flags controlling various window behavior x y w h The X Y location of the window and the width and height of the window The default value of zero indicates that the system should calculate these numbers automatically The main window size and location are stored in abaqus_v6 gpr when the application exits so that when the application is started again it will appear in the same location with the same size Therefore it is recommended that you do not set x y w or h in the main window constructor however if you do those settings will override the settings in abaqus_v6 gpr The following statement shows how you can access the main window mainWindow getAFXApp getAFXMainWindow The layout of the main window is shown in Figure 13 1 13 2 The title bar By default the string shown in the title bar is constructed from the arguments passed into the AFXApp constructor as shown in the following statement AFXApp appName vendorName productName majorNumber minorNumber updateNumber prerelease The title is generated using the format shown in the following statement productName Version majorNumber minorNumber updateNumber For example the following statement AFXApp productName ABAQUS CAE majorNumber 6 minorNumber 4 updateNumber 1 generates the following string in the title bar ABAQUS CAE
163. one N Throw exception User clicks OK GUI processes input and sends command string Exception caught error dialog bot is posted Communication between the kernel and GUI processes GUI COMMANDS 6 3 Kernel commands A kernel command can consist of the following parts object method arguments keywords Commands do not always have an object or even arguments but they will always have a method For example session viewports Viewport 1 setValues width 50 height 100 l 3 29 3 object method arguments mdb models Model 1 PointSection name Section 3 mass 1 0 object method arguments session viewports Viewport 1 bringToFront object method LeafFromElementSets elementSets PART 1 1 E1 method Ran arguments You can type kernel commands in the ABAQUS CAE CLI or you can execute kernel commands from a file by using Run Script Kernel commands are also sent from the GUI process for execution in the kernel Usually the command is sent by the GUI infrastructure as part of normal mode processing see Command processing Section 7 2 4 for details However there are some situations in which you want your application to issue a kernel command from the GUI You can issue kernel commands from the GUI using the sendCommand function Th
164. onents and converts the ABAQUS results into an MSC ADAMS modal neutral file that can be used by the ADAMS Flex program It is the basic reference document for the ABAQUS Interface for MSC ADAMS e ABAQUS Interface for MOLDFLOW User s Manual This document describes how to use the ABAQUS Interface for MOLDFLOW which creates a partial ABAQUS input file by translating results from a MOLDFLOW polymer processing simulation It is the basic reference document for the ABAQUS Interface for MOLDFLOW Installation and Licensing e ABAQUS Installation and Licensing Guide This document describes how to install ABAQUS and how to configure the installation for particular circumstances Some of this information of most relevance to users is also provided in the ABAQUS Analysis User s Manual vi CONTENTS CONTENTS PARTI OVERVIEW 1 Introduction What can I do with the ABAQUS GUI Toolkit 1 1 Prerequisites for using the ABAQUS GUI Toolkit 1 2 ABAQUS GUI Toolkit basics 1 3 Organization of the ABAQUS GUI Toolkit User s Manual 1 4 PART II GETTING STARTED 2 Getting started with the ABAQUS GUI Toolkit What are the components of an ABAQUS GUI application 2 1 Plug ins and customized applications 22 Running the prototype application 2 3 PART II BUILDING DIALOG BOXES 3 Widgets Labels and buttons 3 1 Text widgets 3 2 Lists and combo boxes 3 3 Range widgets 3 4 Tree widgets 3 5 Table widget 3 6 Miscellaneous widgets 3 7 The create
165. only in accordance with the terms of such license This manual and the software described in this manual are subject to change without prior notice No part of this manual may be reproduced or distributed in any form without prior written permission of ABAQUS Inc ABAQUS Inc 2004 All rights reserved Printed in the United States of America U S GOVERNMENT USERS The ABAQUS Software and its documentation are commercial items specifically commercial computer software and commercial computer software documentation and consistent with FAR 12 212 and DFARS 227 7202 as applicable are provided under license to the U S Government with restricted rights TRADEMARKS The trademarks and service marks trademarks in this manual are the property of ABAQUS Inc or third parties You are not permitted to use these trademarks without the prior written consent of ABAQUS Inc or such third parties The following are trademarks or registered trademarks of ABAQUS Inc or its subsidiaries in the United States and or other countries ABAQUS ABAQUS Standard ABAQUS Explicit ABAQUS CAE ABAQUS Viewer ABAQUS Aqua ABAQUS Design ABAQUS Foundation and the ABAQUS Logo Other company product and service names may be trademarks or service marks of their respective owners For additional information see the Trademark and License Notices in the ABAQUS Version 6 5 Release Notes ABAQUS Offices and Representatives ABAQUS Inc Risin
166. ons are set to FRAME RAISED FRAME THICK to provide a standard border You can nest tab books to provide tabs within tabs as shown in the following example tabBookl FXTabBook self None 0 LAYOUT _FILL X FXTabItem tabBookl1 Tab Item 1 tablFrame FXHorizontalFrame tabBookl FRAME RAISED FRAME SUNKEN FXLabel tablFrame This is the region controlled by Tab Item 1 FXTabItem tabBookl1 Tab Item 2 tab2Frame FXHorizontalFrame tabBookl FRAME RAISED FRAME SUNKEN tabBook2 FXTabBook tab2Frame None 0 TABBOOK_ LEFTTABS LAYOUT FILL X FXTabItem tabBook2 Subtab Item 1 None TAB_LEFT subTablFrame FXHorizontalFrame tabBook2 FRAME RAISED FRAME SUNKEN 4 7 TAB BOOKS AFXNote subTablFrame This is a note nin sub tab item 1 nthat extends n over several nlines FXTabItem tabBook2 Subtab Item 2 None TAB_LEFT subTab2Frame FXHorizontalFrame tabBook2 FRAME RAISED FRAME SUNKEN Figure 4 7 shows an example of nested tab books rn mi Tabbed Dialog Figure 4 7 An example of two subtab pages 4 8 LAYOUT HINTS 4 10 Layout hints The FXPacker FXTopWindow and FXGroupBox widgets accept the following layout hints in their children LAYOUT SIDE TOP Attaches a widget to the top side of the cavity LAYOUT _SIDE_TOP is the default layout hint LAYOUT SIDE BOTTOM Attaches a widget to the bottom side of the cavity LAYOUT_SIDE_ LEFT Attaches a widget to the l
167. ont is Helvetica The application can issue a command to change its default font After the command is issued all widgets created by the application use the new font Alternatively you can change an individual widget s font by using the setFont method that is available for many widgets 3 35 WIDGETS AND FONTS are You use the getAFXFont method to obtain the current font setting for a widget Possible fonts FONT PROPORTIONAL FONT_MONOSPACE FONT_BOLD FONT_ITALIC FONT_SMALL The following example shows how you can change the default font for all widgets and the font for a particular widget Get the current default font normalFont getAFXApp getNormalFont Set the font to bold for subsequently created widgets getAFXApp setNormalFont getAFXFont FONT_BOLD FXLabel self Bold font Restore the default font getAFXApp setNormalFont normalFont Set the font of a widget after it is created 1 FXLabel self Sample text 1 setFont getAFXFont FONT_MONOSPACE 3 36 AN OVERVIEW OF LAYOUT MANAGERS 4 Layout managers This section describes how to use the various layout managers in the ABAQUS GUI Toolkit to arrange widgets in a dialog box The following topics are covered e An overview of layout managers Section 4 1 e Padding and spacing Section 4 2 e Horizontal and vertical frames Section 4 3 e Vertical alignment for composite children Section 4 4 e
168. ou can register a toolset with the main window or with a module If you register the toolset with the main window the toolset will be persistent throughout the session for example the File toolset is always available in an ABAQUS CAE session In contrast if you register the toolset with a module the toolset will be swapped in and out with that module s menus and icons for example the Datum toolset is available in an ABAQUS CAE session only in selected modules For more information see Registering toolsets Section 8 2 5 ABAQUS CAE GUI MODULES AND TOOLSETS 10 Customizing an existing module or toolset The previous sections describe how you can create a new module or toolset by starting from an empty base class and adding all the functionality that you need Alternatively you may find that you want to use most of the functionality of an existing module or toolset If a suitable module or toolset exists it may be easier for you to derive a new module or toolset from it and then add or remove functionality from it This chapter describes how to make various modifications to an existing module or toolset The following topics are covered e ABAQUS CAE GUI modules and toolsets Section 10 1 e The Help toolset Section 10 2 e An example of customizing a toolset Section 10 3 10 1 ABAQUS CAE GUI modules and toolsets The ABAQUS GUI Toolkit is designed to allow you to add your own modules and toolsets It is genera
169. owLabels Size tQuantity table showHorizontalGrid TRUE table showVerticalGrid TRUE listId table addList Small tMedium tLarge table setColumnType 0 AFXTable LIST table setColumnListId 0 listId 3 24 TABLE WIDGET Medium Figure 3 26 A combo box within a table cell 3 6 8 Boolean type If you want to allow the user to specify a value in a table be either TRUE or FALSE you must set the type of the column to be BOOL The value of a Boolean item is toggled each time the user clicks the item By default a blank icon represents FALSE and a check mark icon represents TRUE The following example illustrates how you can include Boolean items in a table vf FXVerticalFrame gb FRAME _SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 AFXTABLE_NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table setLeadingRowLabels Nlgeom tStep table showHorizontalGrid TRUE table showVerticalGrid TRUE table setColumnType 0 table BOOL table setColumnWidth 0 50 table setColumnJustify 0 AFXTable CENTER Figure 3 27 Boolean items in a table 3 25 TABLE WIDGET If you do not want to use the default icons you can set your own true and false icons as shown in the following example vf FXVerticalFrame gb FRAME SUNKEN FRAME THICK 0 0 0 0 0 0 0 0 table AFXTable vf 4 2 4 2 None 0 AFXTABLE_NORMAL AFXTABLE EDITABLE table setLeadingRows 1 table
170. ox process them and then hide the dialog box AFXDialog AFXDialog Continue Commit the values in the dialog CONTINUE ID_CLICKED_CONTINUE box hide it and continue collecting input from the user in another dialog box or prompt AFXDialog AFXDialog Apply Same as OK except the dialog box APPLY ID_CLICKED_APPLY is not hidden AFXDialog AFXDialog Defaults Reset the values in the dialog box DEFAULTS ID_CLICKED_DEFAULTS to their defaults AFXDialog AFXDialog Yes Invoke the affirmative action in YES ID_CLICKED_YES response to the question posed by the dialog box AFXDialog AFXDialog No Invoke the negative action in NO ID_CLICKED_NO response to the question posed by the dialog box AFXDialog AFXDialog Cancel Do not commit the values in the CANCEL ID_CLICKED_CANCEL dialog box just hide the dialog box Optionally for the AFXDataDialog a bailout may be posted ifthe user has changed any values since the last commit AFXDialog AFXDialog Dismiss Hide the dialog box without taking DISMISS ID_CLICKED_DISMISS any other action CUSTOM DIALOG BOXES AFXDialog also supports the following options that determine the location of the action area DIALOG_ACTIONS BOTTOM This option places the action area at the bottom of the dialog box and is the default option DIALOG_ACTIONS_RIGHT This option places the action area on the right side of the dialog box DIALOG_ACTIONS_NONE This option does not cre
171. oxes The ABAQUS GUI Toolkit provides a full library of widgets from which you can construct your own dialog boxes However the ABAQUS GUI Toolkit is not designed to allow you to modify existing ABAQUS CAE dialog boxes e Remove ABAQUS CAE GUI modules and toolsets You can choose which GUI modules to include in your application and which GUI modules to leave out For example the ABAQUS Viewer application does not include the modeling related GUI modules it contains only the Visualization module 1 1 ABAQUS GUI Toolkit BASICS e Remove some top level menus or some items in those top level menus For example you could remove the entire top level Viewport menu to prevent users from manipulating viewports or you could remove the Import and Export menu items from the File menu e Perform limited changes to ABAQUS CAE GUI modules and toolsets For more information see ABAQUS CAE GUI modules and toolsets Section 10 1 The ABAQUS GUI Toolkit is not designed to run outside of ABAQUS CAE it must be used with ABAQUS CAE in order for the infrastructure to function properly 1 2 Prerequisites for using the ABAQUS GUI Toolkit To write applications using the ABAQUS GUI Toolkit you need to have some experience in the following areas Python programming You should have some experience with the Python language before you write ABAQUS CAE kernel scripts You should have similar experience when you program GUI applications ABAQUS kernel com
172. p Subsequent examples will extend this example to show how to use more steps from abaqusGui import from plateDB import PlateDB class PlateProcedure AFXProcedure 7 10 PROCEDURE MODES Ha www w w w w m a a m a m m a a a a a m m a a a ay m m a ay my y m m a a my y m m a e m y m ma a e y N def init self owner AFXProcedure __init self owner self cmd AFXGuiCommand self Plate examples self nameKw AFXStringKeyword self cmd name TRUE self widthKw AFXFloatKeyword self cmd width TRUE self heightKw AFXFloatKeyword self cmd height TRUE H ww w w w a m m w a m a m m a a m a m m a a ay ay m m a a ay y m m m a y y ay m a a y y y ma a e y N N ma a def getFirstStep self self cmd setKeywordValuesToDefaults db PlateDB self return AFXDialogStep self db 7 4 2 Procedure constructor You begin writing a procedure mode by deriving a new class from AFXProcedure In the body of the AFXProcedure constructor you must call the base class constructor and pass in the owner which is the module or toolset GUI to which this procedure belongs You then define the commands and keywords needed for the mode The keywords are stored as members of the mode so that they can be accessed by steps If you set registerQuery TRUE in the AFXGuiCommand constructor the mode will query the kernel object specified by the command when it is activated and automatically set the values of the command s keywor
173. pdate the keywords or if the kernel is updated while the dialog box is posted the keywords can update the GUI For more information see Chapter 5 Dialog boxes The following example shows how the form s keywords are connected to the widgets in the dialog box class PlateDB AFXDataDialog def _ init__ self mode PROCEDURE MODES AFXDataDialog init__ self mode Create Plate self OK self CANCEL DIALOG ACTIONS SEPARATOR va AFXVerticalAligner self AFXTextField va 15 Name mode nameKw 0 AFXTextField va 15 Width mode widthKw 0 AFXTextField va 15 Height mode heightKw 0 7 4 Procedure modes A procedure consists of a series of steps that collect input from the user The following topics are covered in this section e Procedure example Section 7 4 1 e Procedure constructor Section 7 4 2 e getFirstStep Section 7 4 3 e getNextStep Section 7 4 4 e getLoopStep Section 7 4 5 e AFXDialogStep Section 7 4 6 7 4 1 Procedure example Steps in a procedure are posted using the following methods e getFirstStep e getNextStep e getLoopStep The following types of steps are available for use in procedures e AFXDialogStep This step provides an interface to a dialog box e AFXPickStep This step provides an interface to allow picking entities in the viewport The following example shows how to write a simple one step procedure mode that uses a dialog box ste
174. procedure you could add a key in option as shown below step AFXPickStep self self pointKwl Select a point POINTS step addPointKeyIn self pointKw2 Ifa step has a key in text field the user enters some values in the text field and the user commits the values by pressing Enter those values will be used in the command Alternatively if a step has a key in 7 17 PICKING IN PROCEDURE MODES text field and the user selects an entity in the viewport that entity will be used in the command regardless of whether anything was typed in the text field The mode automatically takes care of deactivating whichever keyword needs to be deactivated based on these rules In the previous example if the user types in a point selfpointKw1 will be deactivated and self pointKw2 will be activated In addition self pointKw2 will contain the value entered by the user 7 5 7 Picking by angle Picking by face angle or by edge angle is always enabled when appropriate For example picking by face angle is enabled when the user is picking faces You cannot disable picking by angle 7 5 8 Limitations while selecting The following limitations apply to picking procedures e The following entities cannot be picked Sketch entities Features Instances Sets Surfaces XY curve points Skins Picking more than one kind of entity at the same time is not supported for a sequence style of ARRAY for example the user cannot pick nodes and
175. r f Figure 4 2 An example of vertical alignment from AFXVerticalAligner General purpose layout managers The ABAQUS GUI Toolkit includes three general purpose layout managers that have similar layout capabilities FXPacker FXPacker is a general purpose layout manager FXTopWindow FXTopWindow provides similar capabilities to FXPacker Since AFXDialog is derived from FXTopWindow AFXDialog also provides the capabilities of FXTopWindow As a result you do not need to provide a top level layout manager as the first child in a dialog box you can use the layout capabilities of the dialog box instead FXGroupBox FXGroupBox provides the same capabilities as FXPacker In addition FXGroupBox can display a labeled border around its children For example gb FXGroupBox parent Render Style FRAME GROOVE FXRadioButton gb Wireframe FXRadioButton gb Filled FXRadioButton gb Shaded 4 4 RESIZABLE REGIONS 7 Render Style Wireframe C Filled C Shaded Figure 4 3 An example of a group box with a labeled border from FXGroupBox 4 6 Row and column layout manager The FXMatrix widget arranges its children in rows and columns You can perform the layout row wise using the default value of the opts argument MATRIX BY ROWS or column wise by setting opts MATRIX BY COLUMNS If you specify opts MATRIX BY ROWS the matrix will create the specified number of rows and as many columns as are needed to accommo
176. re information see Form modes Section 7 3 Common dialog boxes Common dialog boxes are dialog boxes that provide standard functionality commonly found in many applications The File Selection dialog box is a typical common dialog box These dialog boxes along with other details related to dialog box construction and behavior are described in this chapter Modal versus modeless A dialog box can be either modal or modeless 5 1 SHOWING AND HIDING DIALOG BOXES Modal A modal dialog box prevents interaction with the rest of the application until the user dismisses the dialog box Modeless A modeless dialog box allows the user to interact with other parts of the GUI while the dialog box is posted In ABAQUS CAE all secondary dialog boxes except for tips should be modal dialog boxes A dialog box itself is not defined as modal or modeless the behavior is obtained from the method used to post the dialog box For dialog boxess posted by forms you can set the modal behavior by calling the form s setModal method and providing an argument of either TRUE or FALSE If you call setModal with TRUE as its argument the form will post the next dialog box modally You can call the setModal method several times within one form if you need to change the modal behavior between the various dialog boxes managed by the form For dialog boxes that you post yourself you can use the showModal method instead of the show method described i
177. rey95 FXRGB 242 242 242 Grey96 FXRGB 245 245 245 Grey97 FXRGB 247 247 247 Grey98 FXRGB 250 250 250 APPENDIX B COLORS AND RGB VALUES String RGB value Grey99 FXRGB 252 252 252 Honeydew FXRGB 240 255 240 Honeydew1 FXRGB 240 255 240 Honeydew2 FXRGB 224 238 224 Honeydew3 FXRGB 193 205 193 Honeydew4 FXRGB 131 139 131 HotPink FXRGB 255 105 180 HotPink1 FXRGB 255 110 180 HotPink2 FXRGB 238 106 167 HotPink3 FXRGB 205 96 144 HotPink4 FXRGB 139 58 98 IndianRed FXRGB 205 92 92 IndianRed1 FXRGB 255 106 106 IndianRed2 FXRGB 238 99 99 IndianRed3 FXRGB 205 85 85 IndianRed4 FXRGB 139 58 58 Ivory FXRGB 255 255 240 Ivoryl FXRGB 255 255 240 Ivory2 FXRGB 238 238 224 Ivory3 FXRGB 205 205 193 Ivory4 FXRGB 139 139 131 Khaki FXRGB 240 230 140 Khakil FXRGB 255 246 143 Khaki2 FXRGB 238 230 133 Khaki3 FXRGB 205 198 115 Khaki4 FXRGB 139 134 78 Lavender FXRGB 230 230 250 LavenderBlush FXRGB 255 240 245 APPENDIX B COLORS AND RGB VALUES String RGB value LavenderBlush1 FXRGB 255 240 245 LavenderBlush2 FXRGB 238 224 229 LavenderBlush3 FXRGB 205 193 197 LavenderBlush4 FXRGB 139 131 134 LawnGreen FXRGB 124 252 0 LemonChiffon FXRGB 255 250 205 LemonChiffon1 FXRGB 255 250 205 LemonChiffon2 FXRGB 238 233 191 LemonChiffon3 FXRGB 205 201 165 LemonChiffon4 FXRGB 139 137 112 LightBlue FXRGB 173 216 230 LightBluel FXRGB 191 239 255 LightBlue2 FXRGB 178 223 238 LightBlue3 FX
178. rning Some items failed 13 10 The command line interface The command line interface CLI provides an interface to the kernel side Python command interpreter The CLI does not provide any access to the GUI side Python interpreter The user can enter ABAQUS 13 5 THE COMMAND LINE INTERFACE scripting interface commands in the CLI which are then sent to the kernel for processing In addition the user can enter standard Python commands in the CLI For example the user can use the CLI as a simple calculator as shown in Figure 13 2 gt gt gt len p verti ces gt gt gt 7 27 3 5 14 0 gt gt gt Epa Figure 13 2 The command line interface The ABAQUS GUI Toolkit does not expect users to use the CLI to issue ABAQUS Scripting Interface commands Normally all commands sent from the GUI process are sent by the GUI via modes For more information see Chapter 7 Modes You can hide the CLI if it is not used by your application as shown in the following statements mainWindow getAFXApp getAFXMainWindow mainWindow hideCli 13 6 THE ABAQUS CAE MAIN WINDOW 14 Customizing the main window The main window base class provides the GUI infrastructure to allow user interaction the manipulation of modules and the display of objects in the viewport The main window base class does not provide any application functionality for example building parts This section describes how you assign functiona
179. s argument as a series of patterns separated by n The value of the target specified by the patternIndexTgt argument determines which pattern is initially shown when the dialog box is posted The following is an example of how a file selection dialog box can be posted from a form def getFirstDialog self patterns Output Database odb nAll Files db AFXFileSelectorDialog self Open ODB self nameKw self readOnlyKw AFXSELECTFILE EXISTING COMMON DIALOG BOXES patterns self patternIndexTgt db setReadOnlyPatterns odb self setModal TRUE return db The following is an example of how a directory selection dialog box can be posted from another dialog box def onCmdDirectory self sender sel ptr if not self dirDb self dirDb AFXFileSelectorDialog self Select a Directory self form dirNamekw None AFXSELECTFILE DIRECTORY self dirDb create self dirDb showModal return 1 5 7 2 Print dialog box The Print dialog box provides standard printing functionality To post the Print dialog box from a button in your dialog box you first access the print form mode by using the getPrintForm method of the FileToolsetGui class This can be done by storing a pointer to the form as shown in the following example from sessionGui import FileToolsetGui class MyMainWindow AFXMainWindow Ha ww w w w w w m a w a a m m a y a a m m a e ay m m ma a a y ay ay m m m ay y y m m a y y y m ma a a def _init_ s
180. sage and map it to a message handler in your dialog box For more information see Targets and messages Section 6 4 4 The convention is to use the same name for the message handler as the base class uses for example onCmdApply See Table 5 1 for the full list of message handlers DATA DIALOG BOXES 5 6 Data dialog boxes A data dialog box is a dialog box in which data are collected from the user In contrast a message dialog box displays only a message and a toolbox just holds buttons This section describes how you can create a data dialog box The following topics are covered e An overview of data dialog boxes Section 5 6 1 e Constructor prototypes Section 5 6 2 e Bailout Section 5 6 3 e Constructor contents Section 5 6 4 e Transitions Section 5 6 5 5 6 1 An overview of data dialog boxes A data dialog box is a dialog box in which data are collected from the user In contrast a message dialog box displays only a message and a toolbox just holds buttons AFXDataDialog is designed to be used in conjunction with a mode to gather data from the user The data are then processed in a command You should use AFXDataDialog if you need to issue a command You should also use AFXDataDialog if the dialog box belongs to a module or nonpersistent toolset so that the GUI infrastructure can properly manage the dialog box when the user switches modules The AFXDataDialog class is derived from AFXDialog a
181. se the milestone command to provide feedback on the progress of a volume computation numObjects 4 for i in range numObjects 1 milestone Computing total volume parts i numObjects compute volume here Computing total volume 3 of 4 parts complete 75 Figure 7 2 Displaying the progress of a command 7 2 6 Command error handling If the command sent to the kernel raises an exception the mode infrastructure calls the handleException method The handleException posts an error dialog with the message contained in the exception Alternatively if you want to perform your own error handling you can redefine the handleException method as shown in the following example def handleException self exception exceptionType exception 0 exceptionValue exception 1 Do some special error handling here 7 6 FORM MODES Post an error dialog db self getCurrentDialog showAFXErrorDialog db str exceptionValue 7 3 Form modes A form mode gathers input from the user using one or more dialog boxes This section describes the two methods used by forms for posting dialog boxes The following topics are covered e Form example Section 7 3 1 e Form constructor Section 7 3 2 e getFirstDialog Section 7 3 3 e getNextDialog Section 7 3 4 e Collecting input from the GUI Section 7 3 5 7 3 1 Form example The following example illustrates how to write a form mode
182. ser to specify what should be printed and how it should be printed Modes Modes are GUI mechanisms that control the display of a particular user interface Modes are also responsible for issuing the command associated with that user interface For example a mode is started when you select File gt Print This mode posts the Print dialog box and issues the print command when the user clicks OK Modules and toolsets Modules and toolsets group functionality together A GUI module is a grouping of similar functionality such as the Part module in ABAQUS CAE A GUI toolset is similar to a GUI module in that it groups similar functionality but it generally contains more specific functionality that may 2 1 WHAT ARE THE COMPONENTS OF AN ABAQUS GUI APPLICATION kA ABAQUS Beam Version 1 1 PRE1 Viewport 1 II Ele Mode viewport view beam Hep a x Deus e aO E A gogg Module eam gt Model va ee M art y E Beam Analysis x Model Configuration 7 Geometric Properties Length LU Area 1000 112 100 Ii 200 122 300 akute Material Load Type Force C Pressure Aluminum Magnitude 10 Copper Analyze Cancel bd Executing onCaeStartup in the site directory Executing onCaeStartup in the home directory High level application control asien S
183. sing You can access the string shown in the window title bar using the following statement title getAFXApp getAFXMainWindow getTitle 13 3 THE CONTEXT BAR 13 3 The menu bar The menu bar consists of the following three areas e Persistent toolset menus e Module menus e Help menu The persistent toolset menus and the help menu are shown when the application is first started and they remain visible throughout the user s session The module menus reflect the current module and are swapped in and out as the user visits the various modules You can access the menu bar using the following statement menubar getAFXApp getAFXMainWindow getMenubar 13 4 The toolbar The toolbar consists of the following three areas e Persistent toolset tools e Module tools e Help tools The persistent toolset tools are shown when the application is first started and they remain visible throughout the user s session The module tools reflect the current module and are swapped in and out as the user visits the various modules The help tools which belong to the help toolset are always placed to the right of the other tool buttons You can access the toolbar using the following statement toolbar getAFXApp getAFXMainWindow getToolbar 13 5 The context bar The context bar contains controls for the current module and other context for example the current part You can access the context bar using the followi
184. ssion objects The mdb and session objects in the kernelAccess module mirror their counterparts in the kernel As a result the mdb and session objects in the kernelAccess module are updated whenever the mdb and session objects change in the kernel The GUI side mdb and session objects provide only query access to their kernel side counterpart s attributes they do not allow access to the object s methods You can obtain values from the mdb and session objects using the ABAQUS Scripting Interface For example from kernelAccess import mdb session partNames mdb models Model 1 parts keys odbNames session odbs keys Although you can import the kernelAccess module in a script that is executed before the application startup script has completed you cannot query the mdb and session objects until the application startup script has completed In other words you can import the kernelAccess module in your scripts in code that is executed during the initial construction of the GUI however you should not attempt to access either the mdb or session object until it is needed because of some user interaction in the GUI For more information see Startup script Section 11 2 6 7 Receiving notification of kernel data changes This section describes how the GUI can be notified when kernel objects and custom kernel objects are modified outside the GUI process The following topics are covered e Automatically registering a query on
185. syntax when interpreting the object specified in a GUI command If you place s between square brackets following certain repositories the mode replaces the s with the current name You should always use this s syntax as opposed to hard coding a name so that the current name will always be used in commands The following current objects are supported Object Specification Mode Interpretation session viewports s Current viewport mdb models s Current model mdb models s parts s Current part session odbs s Current output database 6 4 3 Keeping the GUI and commands up to date Ifa command edits an object you should request that a query be registered on that object by specifying TRUE for the registerQuery argument in the GUI command constructor Registering a query will cause the keywords associated with the AFXGuiCommand to be updated with the kernel values when the mode is started and any time the kernel values change For example cmd AFXGuiCommand mode PointSection mdb models s TRUE GUI COMMANDS In addition modes recognize session viewports s as a special repository The mode registers a query on the session automatically so that the command will be kept up to date if the user switches the current viewport The following examples illustrate the special syntax cmd AFXGuiCommand mode setValues session viewports s TRUE cmd AFXGuiCommand mode bringToFront sess
186. t location flag the GUI for that toolset will not appear in that location The table below shows the class name for each of the ABAQUS CAE toolsets along with the flags that indicate the locations in which the toolset create the widgets You can import these class names from abaqusGui When you unregister a toolset you must use the name shown in the table as the argument to the main window s unregisterToolset method Class name Name Toolset locations AmplitudeToolsetGui Amplitude GUL IN_TOOL_PANE CanvasGui Canvas GUL IN MENUBAR DatumToolsetGui Datum GUI_IN TOOLBOX GUI_IN_ TOOL_PANE EditMeshToolsetGui Mesh Editor GUILIN TOOLBOX GUL IN_TOOL_PANE FileToolsetGui File GUL IN MENUBAR GUL IN _ TOOLBAR HelpToolsetGui Help GUL IN MENUBAR GUL IN TOOLBAR ModelToolsetGui Model GUL IN MENUBAR PartitionToolsetGui Partition GUI_IN_ TOOLBOX GUI_IN_TOOL_PANE QueryToolsetGui Query GUI_IN_ TOOLBAR GUL IN_TOOL_PANE RegionToolsetGui Region GUL IN TOOL PANE RepairToolsetGui Repair GUL IN _ TOOLBOX GUL IN_TOOL_ PANE TreeToolsetGui Tree GUL IN MENUBAR ViewManipToolsetGui ViewManip GUL IN MENUBAR GUI IN TOOLBAR 10 2 ABAQUS CAE GUI MODULES AND TOOLSETS The following statements show how you could add your own toolset to the Visualization module File myVisModuleGui py from abaqusGui import from myToolsetGui import MyTools
187. tcher ID OPEN FIRST for the first child You must then increment the message ID from that value for the subsequent children as shown in the following example To use the setCurrent method you should provide the zero based index of the child that you want to display For example to display the first child you should call the setCurrent method with an index value of zero For example hf FXHorizontalFrame parent sw FXSwitcher parent FXRadioButton hf Option 1 sw FXSwitcher ID_OPEN_ FIRST FXRadioButton hf Option 2 sw FXSwitcher ID_OPEN FIRST 1 hf1 FXHorizontalFrame sw FXButton hf1 Button 1 FXButton hf1 Button 2 hf2 FXHorizontalFrame sw FXButton hf2 Button 3 FXButton hf2 Button 4 4 6 TAB BOOKS Option Option 2 Button 1 Button 2 C Option Option 2 Button 3 Button 4 Figure 4 6 An example of a rotating region from FXSwitcher 4 9 Tab books The FXTabBook widget uses tab items to control the display ofits pages one at a time FXTabBook expects that its odd numbered children are FXTabI tems and its even numbered children are some type of layout manager The layout manager contains whatever widgets are to be displayed in that page Clicking a tab item will show the layout manager and all its children associated with that tab while hiding all the other layout managers Typically a horizontal or vertical frame is used for the layout manager and its frame opti
188. th a widget that is in a push state The sequence is as follows 1 First the user enters a value of 7 in the text field and then presses Enter 2 This triggers the text field widget to send an ID SEL_COMMAND message to its target the data target 3 The data target responds by sending the sender the text field widget a message requesting the value in the text field The data target uses that value to update the value of its data ID SEL_COMMAND i Data Target data ID_GETINTVALUE SEL_COMMAND data The user enters a value into the text field Figure 6 3 A data target with a text field widget in push state Pull state In a pull state the widgets are interrogating the application to keep up to date Figure 6 4 illustrates how a data target works with a widget that is in a pull state The sequence is as follows 1 When the GUI is idle it initiates a GUI update 2 The GUI update triggers each widget to send an ID SEL UPDATE message to its target 3 In this case the data target responds by sending the sender the text field widget a message telling it to set its value to the value of the data target s data ID SEL_UPDATE 7 G Data Target data ID_SETINTVALUE SEL_COMMAND data The data target updates the value in the text field Figure 6 4 A data target with a text field widget in a pull state GUI COMMANDS 6 4 7 Option versus value mode A data target works in one of two modes val
189. the base class appIcon FXXPMIcon app appIconData appMinilcon FXXPMIcon app appMinilconData AFXMainWindow init _ self app windowTitle appIcon appMinilcon Register persistent toolsets self registerToolset FileToolsetGui GUI_IN MENUBAR GUI_IN_ TOOLBAR self registerToolset ModelToolsetGui GUI_IN_MENUBAR self registerToolset CanvasToolsetGui GUI_IN_MENUBAR self registerToolset ViewManipToolsetGui GUI_IN MENUBAR GUI_IN_ TOOLBAR self registerHelpToolset HelpToolsetGui 14 2 THE ABAQUS CAE MAIN WINDOW GUI_IN_MENUBAR GUI_IN_TOOLBAR Register modules self registerModule Part Part self registerModule Property Property self registerModule Assembly Assembly self registerModule Step Step self registerModule Interaction Interaction self registerModule Load Load self registerModule Mesh Mesh self registerModule Job Job self registerModule Visualization Visualization self registerModule Sketch Sketch 14 2 2 Importing modules The first statements in the script import the necessary modules The abaqusGui module provides access to the entire ABAQUS GUI Toolkit The Gui modules such as FileToolsetGui provide access to the toolset GUIs that are to be registered with the main window The appIcons module provides access to the icon data needed to construct the icons to be used for the main window 14 2 3 Constructi
190. three choices for the renderStyle argument in display options commands We could number these choices using integer values from 1 to 3 However using integer values would result in a command that is not very readable for example renderStyle 2 Alternatively if we define symbolic constants for each choice the command becomes more readable for example renderStyle HIDDEN Internally symbolic constants contain an integer ID that can be accessed via its getId method Symbolic constants can be used in both the GUI and kernel processes Typically you should create a module that defines your symbolic constants and then import that module into both your kernel and GUI scripts You can import the SymbolicConstant constructor from the symbolicConstants module The constructor takes a single string argument By convention the string argument uses all capital letters with an underscore between words For example from symbolicConstants import SymbolicConstant AS_IS SymbolicConstant AS IS In the case of symbolic constant keywords you can use a value of zero or the value of the ID of a symbolic constant for the message ID Symbolic constants have a unique integer ID that is used to set the value of symbolic constant keywords along with a string representation that is used in the generation of the command To access the integer ID of a symbolic constant use its getId method If the keyword is connected to a list or combo box widget you should use a
191. to be displayed in the Module combo box in CAE and a second that specifies the name of the module to import For more information see Registering modules Section 14 2 5 In most cases you register the module in the main window code by calling the module constructor at the end of the module GUI file If the example shown in GUI module example Section 8 2 resides in a file named myModuleGui py myModuleGui must be used as the second argument to the regis terModule method as shown in the following statement Register modules self registerModule displayedName My Module moduleName myModuleGui Switching to a GUI module To switch to a GUI module that you have instantiated you use the switchModule method For example if you want to switch to your module upon application startup you can add the following line to the application startup file switchModule My Module This line should appear just before the app run statement SWITCHING TO A GUI MODULE You can use the setSwitchModuleHook function method to set a callback function that will be invoked when the user switches into a GUI module Every time the user switches into a GUI module your function will be called and the name of the module will be passed into the function For example def onModuleSwitch moduleName if moduleName Part Do part module tasks elif moduleName Mesh Do mesh module tasks etc setSwitchModuleHook onModul
192. ue or option The examples in the previous section described the value mode You use the value mode when the actual value of some data is of interest In contrast you use the option mode when you require a selection from many items and the value is not of particular importance For data targets operating in the option mode with a widget in the push state the behavior is similar to the value mode described in the previous section When the user clicks a button the button sends an ID SEL COMMAND message to its target In turn the target responds by sending the sender a message requesting it to update the data target s data to the value of the sender s message ID For data targets operating in the option mode with a widget in the pull state the behavior is slightly different from the value mode described in the previous section During a GUI update the data target sends either a check or uncheck message back to the sender depending on whether the sender s ID matches the value of the data target s data For example Figure 6 5 illustrates a data target operating in the option mode with three radio buttons in the pull state Suppose that the value of the data being monitored by the data target is 13 and the message IDs of the radio buttons are 2 13 and 58 respectively The sequence is as follows 1 During a GUI update the first radio button sends a 2 SEL_UPDATE message to the data target 2 The data target compares the message ID 2
193. unctionality that you want you can begin by deriving from that class and then make modifications For more information see Chapter 10 Customizing an existing module or toolset Inside the new class constructor body you must call the base class constructor and pass self as the first argument The moduleName is a string used by the GUI infrastructure to identify this module displayTypes are the flag or flags that specify the type of object that is being displayed in this module Possible values are PART ASSEMBLY ODB XY_PLOT and SKETCH If you specify ASSEMBLY your module must import the assembly kernel module because the assembly kernel module is required to initialize some assembly display options For more information see Kernel module initialization Section 8 2 6 8 2 2 Menu bar items Menu bar items consist of a menu title that controls a menu pane The menu pane in turn contains menu commands Menu commands are buttons that invoke modes GUI MODULE EXAMPLE The example in GUI module example Section 8 2 creates a top level menu pane that contains a submenu The menu commands in the submenu specify the mode that the menu command will invoke by sending the mode an activate message For more information see Mode processing Section 7 2 Figure 8 1 shows the menus and submenus created by the example Menul Item 1 Submenulkd Een Figure 8 1 Creating menus 8 2 3 Toolbar items Toolbar ite
194. ur application needs to import any ABAQUS module other than the Visualization module you must check out a cae token 11 4 Installation You can use a simpler syntax to start an application that has been installed at a site Installing an application involves the following steps 11 3 INSTALLATION e Add an entry to the abaqus_dir site abaqus app file where abaqus_dir is the name of the directory in which ABAQUS is installed To determine the location of abaqus_dir at your site type abaqus whereami at the operating system prompt The format of entries in the abaqus app file is applicationName cae viewer custom startupScript where applicationName is the name that the user must specify on the command line to start the application The second parameter determines the type of token that the application will check out cae or viewer startupScript is the name of the startup script without any file extension The script must reside in a directory specified in the PYTHONPATH environment variable applicationName and startupScript can be the same e Edit the abaqus_dir site abaqus aev file You must add the directory that contains the customization script to the definition of the PYTHONPATH environment variable By convention customization scripts are located in directories underneath abaqus_dir customApps You should add your directory near to the end of the PYTHONPATH definition just prior to the current directory
195. users improve their understanding and usage of ABAQUS see the Training section above for more information about these seminars While not intended as stand alone tutorial material they are sufficiently comprehensive that they can usually be used in that mode The list of available lecture notes is included in the Documentation Price List Documentation Information e Using ABAQUS Online Documentation This online only manual contains instructions for viewing and searching the ABAQUS online documentation Reference e ABAQUS Keywords Reference Manual This volume contains a complete description of all the input options that are available in ABAQUS Standard and ABAQUS Explicit e ABAQUS Theory Manual This online only volume contains detailed precise discussions of all theoretical aspects of ABAQUS It is written to be understood by users with an engineering background e ABAQUS Verification Manual This online only volume describes more than 12 000 basic test cases providing verification of each individual program feature procedures output options MPCs etc against exact calculations and other published results It may be useful to run these problems when learning to use a new capability In addition the supplied input data files provide good starting points to check the behavior of elements materials etc e Quality Assurance Plan This document describes the QA procedures followed by ABAQUS It is a controlled document provide
196. value of zero for the ID in the widget constructor The AFXList AFXComboBox and AFXListBox widgets have been designed to handle symbolic constant keywords as targets When items are added to a list or combo box a symbolic constant s ID is passed in as user data These widgets react by setting their value to the item whose user data matches the value of their target as opposed to setting their value to the item whose index matches the target s value The following example illustrates how a combo box can be connected to a symbolic constant keyword combo AFXComboBox hwGb 18 4 Highlight method mode highlightMethodHintkKw 0 combo appendItem Hardware Overlay HARDWARE OVERLAY getId combo appendItem Software Overlay SOFTWARE OVERLAY getId combo appendItem XOR XOR getId combo appendItem Blend BLEND getId Ifthe keyword is connected to a radio button you should use the ID ofthe symbolic constant that corresponds to that radio button for the message ID Since the ID of all symbolic constants is greater than zero this tells the keyword to operate in option mode The following example illustrates how symbolic constant keywords can be used with radio buttons GUI COMMANDS from abaqusConstants import Modeling Space gb FXGroupBox self Modeling Space FRAME GROOVE LAYOUT_ FILL X FXRadioButton gb 3D mode dimensionalityKw THREE D getId LAYOUT _SIDE_LEFT FXRadioButton gb 2D Planar
197. where each part is separated by t The three parts of the text string are Text The text displayed by the widget Tip text The text displayed when the cursor is held over the widget for a short period of time If there is only an icon associated with a widget you must supply the tip text Help text The text displayed in the application s status bar assuming that the application has a status bar In addition you can define a keyboard accelerator for the widget by preceding one of the characters in the text with an ampersand amp character For example if you specify the string amp Calculate for a button the button label will appear as shown in Figure 3 1 You can use the accelerator to invoke the button by pressing the Alt key along with the C key Calculate Figure 3 1 A keyboard accelerator applied to a button 3 1 2 Labels The FXLabel widget displays a read only string FXLabel can also display an optional icon FXLabel parent This is an FXLabel tThis is nthe tooltip This is an FXLabel Figure 3 2 An example of a text label from FXLabel 3 1 3 Push buttons The FXButton widget contains a label and or an icon When the user clicks the button an immediate action is invoked FXButton parent This is an FXButton LABELS AND BUTTONS This is an FXButton Figure 3 3 An example of a button from FXButton 3 1 4 Check buttons The FXCheckButton widget provides an On Off toggling capability
198. word s value The prototypes for all the keywords are similar The first two arguments of a keyword are e A GUI command object e A String specifying the name of the keyword All keywords also support an argument that determines whether the keyword is required or optional If a keyword is required it will always be sent with the command If a keyword is optional it will be sent only if its value was changed Most keywords support the specification of a default value When you construct a keyword its value is set to the default value If you use the keyword s setDefaultValue method to change the default value you will not affect the value of the keyword unless you also call the keyword s setValueToDefault method In contrast if you want to change only the value of the keyword without changing its default value you should use the keywords setValue method When the mode issues the command to the kernel the keywords will be ordered in the same order in which they were created in the mode When storing keywords in the mode class the convention is to name the keyword object using the same name as the keyword label plus Kw For example self rKw AFXIntKeyword self cmd r TRUE self tKw AFXFloatKeyword self cmd t TRUE self nameKw AFXStringKeyword cmd name TRUE Part 1 GUI COMMANDS self twistKw AFXBoolKeyword cmd twist AFXBoolKeyword ON OFF 0 self typeKw AFXSymConstKeyword cmd type TRUE SHADED
199. yle of the command generated by the mode you can redefine this method to generate your own command string e sendCommandString This method takes the command string returned from the getCommandString method and sends it to the kernel for processing 7 4 MODE PROCESSING e doCustomTasks This method has an empty implementation in the base class You can redefine this method to perform any additional tasks required after a command is processed by the kernel After calling these methods the issueCommands method will deactivate the mode if the user presses the OK button In most cases you do not need to call issueCommands however if you interrupt the normal flow of mode processing you must call issueCommands to complete the processing For example if before issuing a command you want to ask the user to click an OK button to overwrite a file you can post a warning dialog box from thedoCustomChecks method In this example you must return FALSE from the doCustomChecks method to stop the command processing The application will then wait for the user to make a selection from the warning dialog box When the user clicks a button in the warning dialog box you must catch the message sent by the dialog box to your form If the user clicks Yes you should continue the command processing as shown in the following example class MyForm AFXForm ID_OVERWRITE AFXForm ID LAST def _ init__ self owner AFXForm init self owner FXMAPFUNC s
200. yout button acts as a regular button A flyout button displays an icon for the current function along with a triangle in the lower right corner Figure 8 2 shows the flyout buttons created by the example 8 2 GUI MODULE EXAMPLE Flyout Button 2 Figure 8 2 Toolbox flyout buttons 5 Registering toolsets Modules can include toolsets simply by registering them Toolsets that are registered with a module will be available when that module is the current module To register a toolset you supply a pointer to the toolset along with bit flags that specify where in the GUI the toolset has defined components The following locations are supported FLAG LOCATION IN GUI GUL_IN_NONE Toolset has no components in standard locations GUI IN MENUBAR Toolset has components in the menu bar GUI_IN_TOOL_PANE Toolset has components in the Tools menu pull down pane GUI IN TOOLBAR Toolset has components in the toolbar GUI_ IN TOOLBOX Toolset has components in the toolbox 8 2 The example in GUI module example Section 8 2 registers a toolset that contains elements in the main menu bar and the Tools menu If you do not specify a flag in an area in which you have created some GUI components those components will not be shown in the application 6 Kernel module initialization In general aGUI module is designed to provide an interface to a kernel module After the GUI collects input from the user it constructs

ABAQUS GUI Toolkit User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents