group attributes
Allows the specification of attributes to be set on a group
Format:
group attributes |
|---|
group_name = | an existing group |
scale_of_icons = | real |
size_of_icons = | real |
visibility = | on_off_with_toggle |
name_visibility = | on_off_with_toggle |
color = | an existing color |
line_thickness = | real |
line_type = | line_style |
entity_scope = | color_scope |
active = | on_off_no_opinion |
dependents_active = | on_off_no_opinion |
member_dependents_active = | on_off_no_opinion |
Example:
group attributes & |
|---|
group_name = | group_1 & |
scale_of_icons = | 0.90 & |
visibility = | on & |
name_visibility = | on & |
color = | blue & |
line_thickness = | 0.19 & |
line_type = | dash & |
entity_scope = | fill_color & |
active = | on d & |
dependents_active = | on |
member_dependents_active = | on_off_no_opinion |
Description:
Parameter | Value Type | Description |
|---|
group_name | An Existing Group | Specifies the group to be modified. You use this parameter to identify the existing group to be affected with this command. |
scale_of_icons | Real | Specifies a unit-less scale factor to apply to the current icon size. |
size_of_icons | Real | Specifies the size, in modeling units, the Adams View icons will appear in. |
visibility | On / Off / No_opinion / Toggle | Specifies the visibility of graphic entities |
name_visibility | On / Off / No_opinion / Toggle | The NAME_VISIBILITY parameter provides control over the visibility of the view name displayed at the top center position of a given view. |
color | An Existing Color | Specifies the color the modeling entity should be drawn in. |
line_thickness | Real | Specifies the thickness of the line for a curve |
line_type | Line_style | This parameter allows the selection of the line type for a curve. |
entity_scope | Color_scope | The ENTITY_SCOPE parameter is used to control how a color modification is to affect a particular graphic entity. |
active | On / Off / No_opinion | Controls the activity of the group and thereby all objects in the group. Specifying no_opinion leaves the existing activity state unchanged.
When you set ACTIVE=OFF, that element is written to the data set as a comment. |
dependents_active | On / Off / No_opinion | Specifies whether dependents of the objects are to be acted upon in the same way as the active parameter does. |
member_dependents_active | On / Off / No_opinion | Controls the activity of the dependents of all objects in the group |
Extended Definition:
1. If a group has attributes associated with it, any object in the group will inherit the group's attribute. If an object is in more than one group, the object will inherit the attribute of the last group it was added to.
2. You may identify a group by typing its name.
If a group is available by default, you may identify it by entering only its name. If it is not, you must enter its full name. If you type a "?", Adams View will list the group available by default.
You must separate multiple group names by commas.
3. If no initial size is specified for Adams View icons, the default size will be one modeling LENGTH unit. For example, if the modeling units are K/M/S, a part axes icon will have triad legs of one meter in length.
When you specify SCALE_OF_ICONS, a new size is calculated by multiplying the current size by the scale, and storing the product as the new ICON_SIZE.
4. If no initial size is specified for Adams View icons, the default size will be one modeling LENGTH unit. For example, if the modeling units are K/M/S, a part axes icon will have triad legs of one meter in length.
When you set SIZE_OF_ICONS at the model level, all Adams View icons used in creating a model will use the size specified.
If the model has an SIZE_OF_ICONS set, and a part under that model has a different SIZE_OF_ICONS, the model's ICONS_SIZE will take precedence.
For Example:
.model ---------------------- SIZE_OF_ICONS =.15 meters
.part -------------------- SIZE_OF_ICONS = .125 meters
The part's icon will be 1.5 meters is size.
If the model has SIZE_OF_ICONS of set to 0.0 , and a part under that model has a SIZE_OF_ICONS set to .125, the part's icon size will be used.
For Example:
.model ---------------------- SIZE_OF_ICONS = 0.0 meters
.part -------------------- SIZE_OF_ICONS = .125 meters
The part's icon will be .125 meters is size.
5. 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.
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 entities visibility and reverse it.
6. The legal values of the name_visibility parameter are ON and OFF. This is an optional parameter and if not entered the name will be visible (i.e. will be ON).
Note that if the visibility of the view name is turned off the only indication that a view is "active" will be the color of the viewport border. This would be a problem on a black and white monitor.
7. 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.
8. The line type describes how the line will look when displayed on a plot. Adams View supports solid, dash, dotdash, and dot.
Line Type Appearance
-------------------------------------
solid _______________
dash _ _ _ _ _ _ _ _
dotdash . _ . _ . _ . _
dot . . . . . . . .
9. The legal values for the entity_scope parameter are FILL_COLOR, EDGE_COLOR,OUTLINE_COLOR, and ALL. FILL_COLOR is the color of those areas of a graphic that can be shaded (they include sides of a cylinders, frustums, boxes, etc.) The EDGE_COLOR is the color of the lines making up the edges of the facets (or areas filled by the FILL_COLOR) of a graphic that can be shaded.
The OUTLINE_COLOR represents the color of the lines that make up those graphics that cannot be shaded or filled, like an outline graphic statement consisting of two points or the coil of a springdamper.
Finally, the ALL value indicates that all three entity types, FILL_COLOR, EDGE_COLOR, and OUTLINE_COLOR will be affected by the color change.
The ENTITY_SCOPE parameter is optional and if not entered, will be set to FILL_COLOR.
10. 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.
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
MEMBER_DEPENDENTS_ACTIVE parameter acts in the same fashion as the DEPENDENTS_ACTIVE parameter, but it operates on the dependencies of each object in the group