output_control attributes request
Allows you to change the color and visibility of a request icon.
Format:
output_control attributes request |
|---|
request_name = | .model.request_name |
visibility = | on/off |
color = | color_string |
active = | on/off |
dependents_active = | on/off |
Example:
output_control attributes request & |
|---|
request_name = | .model.m01 & |
visibility = | on & |
color = | PINK & |
active = | on & |
dependents_active = | off |
Description:
Parameter | Value Type | Description |
|---|
request_name | String | Specifies the request to be modified. You use this parameter to identify the existing request to be affected with this command. |
visibility | String | Specifies the visibility of graphic entities. The visibility parameter is used to control whether graphic entities, such as markers, joints, and parts, are to be drawn in an Adams View viewport. |
color | String | Specifies the color the modeling entity should be drawn in. |
active | On/Off/No_opinion | When you set ACTIVE=NO, that element is written to the data set as a comment. |
dependents_active | On/Off/No_opinion | The DEPENDENTS_ACTIVE parameter acts in the same fashion as that of the ‘active’ parameter, but sets the ACTIVE attribute for the dependents all the way down the dependency chain. |
Extended Definition:
1. You may identify a request by typing its name. If you created the request by reading an Adams data set or graphics file, the request name is the letters MRE followed by the Adams data set request ID number. For example, the name of Adams MREQ/101 is MRE101. If you created the request during preprocessing, you will have given it a name at that time. If a request is available by default, you may identify it by entering only its name. If it is not, you must enter its full name. To identify a request under another analysis, for instance, you may need to enter the analysis name as well. For example, you may specify request 101 from the analysis named test by entering ".test.req101".
2. The visibility parameter is used to control whether graphic entities, such as markers, joints, and parts, are to be drawn in an Adams View viewport. The legal values for this parameter are: ON, OFF, and TOGGLE. ON will make the desired entity visible. OFF will make the desired entity invisible. TOGGLE will take the current state of an entity’s visibility and reverse it.
3. Specifies the color the modeling entity should be drawn in. Adams View allows you to specify the following colors for modeling entities: BLACK, WHITE, RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and NO_COLOR. Specifying 'NO_COLOR' for a modeling entity, instructs Adams View to use the default color for this entity, if there is no color present in its parent modeling entity.
Example 1
.model -------------------------NO_COLOR
.part ---------------------- RED
.geometry(circle) ------- NO_COLOR
The circle will be RED.
Example 2
.model -------------------------NO_COLOR
.part ---------------------- RED
.geometry(circle) ------- BLUE
If a parent modeling entity has a color previously specified, that color takes precedence. Adams View will issue a warning message about color precedence. The circle will be RED.
Example 3
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
.geometry(circle) ------- BLUE
The circle will be BLUE.
4. When you set ACTIVE=NO, that element is written to the data set as a comment. When you set the ACTIVE attribute on an object, you are also setting it on the children of the object. If you set ACTIVE=NO on a part, but wish for a marker on that part to be on, then you must explicitly set ACTIVE=YES on the marker, after setting activation on the part.
5. The DEPENDENTS_ACTIVE parameter acts in the same fashion, but sets the ACTIVE attribute for the dependents, all the way down the dependency chain. For example, if you execute the following command:
PART ATTRIBUTES PART=PAR1 DEPENDENTS_ACTIVE=NO
Where PAR1 has a marker MAR1 which is the I marker of a joint JOI1 (which has a J marker MAR2), then JOI1 will be deactivated. Also, if the joint JOI1 is referenced in a request function, or if the I marker is referenced by a request, then the request will be deactivated. Propagation of activation status through groups is as if each element were to have its activation status changed individually.
Elements affected are:
■Group
■Part
■Differential Equation
■Marker
■Geometry
■Constraints
■Forces
■Data Elements
■Output Control
Tips:
1. If you type a "?", Adams View will list the requests available by default.