*BeginDefinitions() Block
The *BeginDefinitions() block contains all program session interface definitions. For example, all report definitions are included in this block.
View new features for HyperWorks Desktop 2022.2.
Learn the basics and discover the workspace.
Discover HyperWorks Desktop functionality with interactive tutorials.
Start HyperWorks Desktop and configure the applications.
Learn how to start HyperWorks Desktop applications on Windows and Linux.
HyperMesh Batch is a non-graphical version of HyperMesh that can be used to run command files or Tcl scripts in batch mode.
The start-in directory is the location from which the HyperWorks Desktop application is launched.
HyperWorks Desktop writes several different settings files.
There are various types of startup customizations that are possible for HyperWorks Desktop. These items define how the application looks or behaves at product startup.
HyperMesh allows you to create a script file named hmcustom.tcl that can be used to automatically execute a series of commands or to define custom settings during startup.
Environment variables can be defined to configure various aspects of HyperWorks Desktop.
Extension are programs integrated with HyperWorks to enhance or extend the user experience.
A preference file is an ASCII file that configures the application or its clients. It specifies default user settings, such as the order in which colors are assigned, the default printer and default page layout.
A session file is an ASCII text file that contains a structured list of session statements.
Session files always begins with the *Id() statement which is followed by statements grouped in blocks.
The *BeginPage() block includes all instructions for the page layout and window content.
The *BeginDefinitions() block contains all program session interface definitions. For example, all report definitions are included in this block.
The *BeginPalette() block contains instructions for any user-defined graphic palettes that are included in the work session.
The *BeginStatsTemplates() block contains instructions for any user-defined statistics templates that are included in the work session.
When a session is saved, filenames are stored as Templex variables. When a session file is loaded, the program checks for Templex statements in the session file.
Report templates are ASCII text files that contain statements for creating reports.
Create, open, import, and save models.
Control the view and display of your model in the modeling window.
Use the Session Browser to view the current session and all the pages and windows it contains in a hierarchical display.
Publish your HyperWorks Desktop session to HTML, PowerPoint, or Report files.
Use the Parameters Browser to parameterize the contents of a session file or report template and automate a variety of analysis processes.
Automate common workflows using the Process Manager or Automate tool.
Explore, organize and manage your personal data, collaborate in teams, and connect to other data sources, such as corporate PLM systems to access CAD data or publish simulation data.
Overview of external readers and the Altair Binary Format, the generic ASCII reader, running HyperWorks in batch mode, using Tcl/Tk commands, translators, and result math.
Start HyperWorks Desktop and configure the applications.
There are various types of startup customizations that are possible for HyperWorks Desktop. These items define how the application looks or behaves at product startup.
A session file is an ASCII text file that contains a structured list of session statements.
Session files always begins with the *Id() statement which is followed by statements grouped in blocks.
The *BeginDefinitions() block contains all program session interface definitions. For example, all report definitions are included in this block.
The *BeginDefinitions() block contains all program session interface definitions. For example, all report definitions are included in this block.
© 2023 Altair Engineering, Inc. All Rights Reserved.
Intellectual Property Rights Notice | Technical Support | Cookie Consent