data_element attributes
Allows the specification of attributes to be set on an individual data_elements or a group of data_elements.
Format:
data_element attributes |
|---|
data_element_name = | an existing var |
visibility = | on_off_with_toggle |
color = | an existing color |
active = | on_off_no_opinion |
dependents_active = | on_off_no_opinion |
Exam ple:
data_element attributes & |
|---|
data_element_name = | shaft_genstiff & |
visibility = | on & |
color = | blue & |
active = | on & |
dependents_active = | on |
Description:
Parameter | Value Type | Description |
|---|
data_element_name | An Existing Var | Specifies an existing data_element. |
visibility | On_off_with_toggle | Specifies the visibility of graphic entities. |
color | An Existing Color | Specifies the color the modeling entity should be drawn in. |
active | On_off_no_opinion | Set the activation of the element |
dependents_active | On_off_no_opinion | Set the activation of the dependants of an element |
Extended Definition:
1. You can set the following attributes on a data_element.
VISIBILITY. You may set a data_element's visibility ON, OFF or TOGGLE the current setting. When you set a data_element's visibility OFF, the data_element will not be drawn.
When you set a data_element's visibility ON, you allow that data_element to be drawn.
COLOR. You may set the color of a data_element with this parameter.
If an entity does not have a GRAPHICS ATTRIBUTE setting, the value for that GRAPHIC ATTRIBUTE may be inherited from another entity. INHERITANCE may be either TOP_DOWN or BOTTOM_UP.
2. BOTTOM_UP and TOP_DOWN refer to the natural hierarchy of the Adams model. The hierarchy is a tree structure with the model at the apex. Parts exist beneath the model, and markers exist beneath the parts. If the icon size of the model is set to 0.1, and the default INHERITANCE is set to TOP_DOWN, then all icons displayed within the model will be displayed at this size. However, if the icon size of a model is set to 0.1, and then the default INHERITANCE is set to BOTTOM_UP, then any icons set to a size other than the model's icon size will be displayed at their own size.
3. You may identify a data_element by typing its name or by picking it from the screen.
Since data_element do not have a geometric position, Adams View displays data_element icons at or near the model origin. If the data_element icon is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the data_element icon is displayed.
You must separate multiple data_element names by commas.
If the data_element is visible in one of your views, you may identify it by picking on any of the graphics associated with it.
You need not separate multiple data_element picks by commas.
4. 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.
5. 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.
6. 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.
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 indvidually.
Elements affected are:
♦Group
♦Part
♦Differential Equation
♦Marker
♦Geometry
♦Constraints
♦Forces
♦Data Elements
♦Output Control