-->(M_REDO)-->
M_REDO (Multiple Redo) command redos the effect of previously undone user action.
-->(M_UNDO)-->
M_UNDO (Multiple Undo) command undos the effect of the previous user action.
Note: Not every command (user action) is supported. Unsupported commands will clear the undo stack.
+---------------------<-------------------+
| |
V |
->(MAKE_QUERY_PAGE)--|qpname|-+(ATTRIBUTE)---|attrname|---|colwidth|--->+
|
+<--------------------<-----------------------<---------------------+
| |
+------------------------------>+ +----------------------------->+ |
| | | | |
+-|DISP COLOR|->+-------------->+->+-|DISP_TEXT|->+-------------->+>+
| | | | |
+-|BCKG COLOR|->+ +|ACTION_TEXT|->+ |
|
+---------------------<-----------------------<---------------------+
| |
| +----------<------------+ |
| V | |
+(COLUMN)+-------------------------->+--->+-(LEFT)--------------->+>+->(END)
| | | |
+|DISP COLOR|+------------->+ +-(RIGHT)-------------->+
| | | |
+|BCKG COLOR|->+ +-(CENTER)------------->+
| |
+-(FORMAT)-|PRECISION|->+
| |
+-|ACTION_TEXT|-------->+
| |
+-|LOG_TAB_COL|-------->+
Create a new named query page for use with DMS applications. Here is an example showing the minimum form of this command:
EXAMPLE:
MAKE_QUERY_PAGE 'page1' ATTRIBUTE 'att1' 15
ATTRIBUTE 'att2' 10
END
This creates a query page whose name is 'page1' containing two attributes: 'att1' and 'att2'. The width of the column containing att1 is 15 characters and the width of the column containing att2 is 10 characters. Default values are assigned for all of the other title and column settings. These defaults are:
Title Settings:
Action Text: 'att1' for title 1 and 'att2' for title 2
Display Text: 'att1' for title 1 and 'att2' for title 2
Disp Color: BLACK
Bckg Color: CYAN
Column Settings:
Disp Color: Green
Bckg Color: Black
Justification: LEFT
Format precision: 3 decimal places
Action Text: Contents of corresponding column in logical table
Log_tab_col: Set by paging code
As many attibutes as required may be added to a query-page but the columns will be squeezed to fit into the display table layout to which the query-page is attached. An example of a full query page specification follows:
EXAMPLE:
MAKE_QUERY_PAGE 'page2' ATTRIBUTE 'att1' 15 'Att1' 'LINE' BLUE BLACK
COLUMN RED MAGENTA RIGHT FORMAT 5
ATTRIBUTE 'att2' 10 'Att2' 'LINE' GREEN YELLOW
COLUMN BLACK WHITE CENTER FORMAT 2
END
Here no action text has been specified for the column, it will be assigned by the paging code when pages are assigned. The action text for the two titles will invoke the LINE command. The default colors for the titles and the display columns have been overridden, as have the column default justification and format.
Returns a unique filename for temporary use.
The MANAGE menu allows access to the CoCreate/DMS management functions. These functions allow the user to create, remove, release, unrelease and update elements.
This section describes the mapping options MOVE, ROTATE, MIRROR, SCALE, SIMILAR, and AFFINE in the MODIFY and STRETCH commands.
In each option, DEL_OLD means that the original geometry is modified, and COPY means that the geometry is copied before modification. The default is always DEL_OLD.
Each option also accepts a repeat factor. The repeat factor tells how many times the modification should be repeated. Thus, a COPY with repeat factor 5 results in 5 copies, plus the original. You can also use a repeat factor with DEL_OLD for (primitive) kinematic investigations. For example, you can ROTATE a robot arm a little at a time to see at what point it touches some other element.
It is possible to select elements, then apply several transformations to them, within one invocation of MODIFY or STRETCH. If you are working this way, and you change the repeat factor, this factor stays in effect for subsequent modifications, until you leave the command. The exception is MIRROR, which always sets the repeat factor back to 1.
The descriptions somewhat loosely speak of "elements"; with STRETCH it is sometimes only one end of an element that is modified.
Returns 1 if the first string is matched by the pattern specified by the second string, otherwise returns 0. The pattern may contain wildcards as follows:
* Matches any string including the null string.
? Matches any single character.
[...] Matches any one of the enclosed characters. A pair of characters
separated by a hyphen (-) matches any character lexically between the
pair, inclusive. A NOT operator, !, can be specified immediately
following the left bracket to match any single character not enclosed
in the brackets.
\ Removes any special meaning of the following character.
Any other character matches itself.
-->(MAX_FEEDBACK)--------->|number|---------->
With MAX_FEEDBACK you can specify how much element tracking you want in the MODIFY and STRETCH command (default is 20 feedback points). Tracking one line costs two feedback points, one arc five points.
-->(MEASURE_ANGLE)-+-------------+-->|pnt 1st elem|-->|pnt 2nd elem|-->
| |
`->-(ASSIST)--'
MEASURE_ANGLE measures the angle between the two identified elements. The angle is measured from the first element to the second, counterclockwise.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
The ASSIST qualifier switches on user assistance (COPILOT command). Additional graphical feedback and creation methods are then available.
---->(MEASURE_AREA)---->|id_point|---->
MEASURE_AREA measures the area enclosed by the identified circle, arc, spline, or fillet.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
---->(MEASURE_COORDINATE)---->|point|---->
MEASURE_COORDINATE measures the coordinates of the indicated point.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
->(MEASURE_DISTANCE)->+----------------->+->|xy id_point|->|xy id_point|-->
| |
+-->(HORIZONTAL)-->+
| |
+--->(VERTICAL)--->+
| |
`---->(ASSIST)-----'
MEASURE_DISTANCE measures the distance between the indicated points. HORIZONTAL or VERTICAL specifies the horizontal or vertical distance; this is independent of the input coordinate system.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
The ASSIST qualifier switches on user assistance (COPILOT command). Additional graphical feedback and creation methods are then available.
---->(MEASURE_LENGTH)---->|id_point|---->
MEASURE_LENGTH measures the length of the identified line, circle, arc, fillet, or spline.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
---->(MEASURE_RADIUS)---->|id_point|---->
MEASURE_RADIUS measures the radius of the identified circle, arc or fillet.
If the system is being used interactively, the value is written in the keyboard input buffer so it can be used as input without retyping.
The value is also written into the system inquiry array (see INQ). During the measure functions ruler follow is off.
MEDIR ===> string
Returns the contents of the MEDIR environment variable. If not set, MEDIR returns a zero length string ("").
Returns the ME10 home directory. On Windows platforms returns
If you run out of memory completely, the system gives you a SYSTEM ERROR message to that effect. IF THIS HAPPENS, YOU SHOULD *IMMEDIATELY* STORE WHAT YOU ARE WORKING ON, EXIT, AND RE-ENTER THE SYSTEM. You can then try to free up some space by deleting part of the drawing, unused fonts, or whatever. It is important to store and exit after running out of memory, as the system cannot recover from this error a second time.
-->(MENU)-->+---->|display_color|---->+---->|background_color|---->,
| | |
v v v
+<------------------------+<---------------------------'
|
v
+---->|display_text|---->+---->|action_text|---->,
| | |
v v v
+<-----------------------+<----------------------'
|
v
+---->(DITHER)---->,
| |
| v
+<-----------------;
|
v
+---->|row|---->|column|----------------------------->,
| |
v v
'->(BOX)->|startrow|->|startcol|->|endrow|->|endcol|->+---->
MENU defines the appearance and the action of screen menu slots. Unspecified items retain their old (previous) values. The screen is not updated every time the MENU function is invoked, but rather when the next user input is requested. The UPDATE_SCREEN or NEW_SCREEN functions may be used to show changes immediately.
display_color: color of the text or drawing in the menu slot background_color: color of the menu slot background display_text: text defining the appearance of the menu slot (see below) action_text: text used as input if the menu slot is picked DITHER: if not present, the background_color will not be dithered row: row number of the selected menu slot col: column number of the selected menu slot startrow: row number of the first selected menu slot startcol: column number of the first selected menu slot endrow: row number of the last selected menu slot endcol: column number of the last selected menu slot
Instead of entering a row and column number pair, you can pick the required menu slot.
If the first character of the display_text has an ordinal value of 255, then the display_text is not displayed literally, but it is interpreted as a graphic menu icon command string. The format of such a graphic menu icon command string is:
,<----------------------------------------+<------------------------, | ^ ^ | | | v v | -->+-->|move opcode|-->|x_move|-->|y_move|-->+-->|x_draw|-->|y_draw|-->+-->
move opcode: character with ordinal value 255. x_move, y_move, x_draw, y_draw: characters with ordinal values of 0...254.
MENU 1 brings up the DIMENSION 1 screen menu.
MENU 2 brings up the DIMENSION 2 screen menu.
MENU 3 brings up the DIMENSION 3 screen menu.
,<-------------------------,
| ^
v |
---->(MENU_LAYOUT)---->+---->+-------------->+---->+---->|point|---->+---->
| | | |
+--->(UPPER)--->+ `----->(END)----->'
| |
+--->(UPPER)--->+
| |
+--->(LOWER)--->+
| |
+--->(RIGHT)--->+
| |
+--->(LEFT)---->+
| |
+-->|height|--->+
| |
`-->|string|--->'
MENU_LAYOUT defines the shape and the location of a menu. Height is a number specifying the height of the next menu row in pixels. The default value for height is the character height (the exact value depends on the font used). String contains information about the menu width and the arrangement of the menu slots. There must be one string per row of the menu. Within a string, menu slots are separated by a bar '|'. The number of characters between bars shows the width (in characters) of the corresponding slot; the actual characters are irrelevant, and are typically blanks or digits.
If no string is given, the existing menu layout is moved to the specified location. The default location is the LOWER RIGHT corner.
As the MENU_LAYOUT function is mostly used in personality macros, it does not automatically remove any old screen menu from the screen. The display of the new screen menu is deferred until the next user input is requested. The UPDATE_SCREEN or NEW_SCREEN functions may be used to show changes immediately.
The MENU_LAYOUT function initializes all menu slots with the following values:
MEPELOOK=0 MEPELOOK=1
display_color: WHITE WHITE background_color: BLACK GREY display_text: '' '' action_text: '' ''
You then use MENU to change these values.
Example:
MENU_LAYOUT UPPER RIGHT
'123456789012| | | | | '
' | | | | | '
50 ' | '
' | '
END
This defines a menu in the upper right corner of the screen. There are four lines in the menu, each the width of 23 characters. The first two lines have six slots, the second, two. The first slot in each row can contain up to 12 characters. The third line is 50 pixels high.
---->(MENU_STATUS)---+-->(MOVE)------>|point|--->+--->
| |
+-->(MAP)------------------>+
| |
+-->(UNMAP)---------------->+
| |
+-->(FIX)------------------>+
| |
+-->(UNFIX)---------------->+
| |
+-->(FIX_UNFIX)------------>+
| |
+-->(ENABLE_INQ)----------->+
| |
+-->(DISABLE_INQ)---------->+
The MENU_STATUS function can be used to change the status of the current menu:
MOVE moves the current menu to the new position 'point'.
MAP causes the current menu to appear on the screen. If the current
menu is already on the screen it will be shuffled up to be fully
visible.
UNMAP causes the menu to disappear from the screen.
FIX fixes the current menu at its current position. If the menu is
unmapped and then mapped again it will appear at this position.
UNFIX resets the map position to the home position.
FIX_UNFIX switches the current menu from fixed to unfixed or from unfixed
to fixed, dependent on the current state.
ENABLE_INQ makes the menu layout accessible through the next menu field of
INQ_MENU.
DISABLE_INQ makes the menu inaccessible through the next menu field of
INQ_MENU. This is the default value for menu layouts.
,-------------------------------------------------,
v ^
-->(MERGE)--+-->|elem 1|--->|elem 2|---+-->|merge pnt|---->+--+--->
| | ^ |
| '-------------------' |
`-->|selection|-----------------------------------'
MERGE causes two elements to be merged into a single one. You can merge elements if they are of the same type. The merge is allowed only where it makes sense, for example, the lines must point in the same direction and have a common end point, and the arcs or fillets must have the same center and radius. If two arcs forming a circle are merged, the user must choose one of the two common points for the merge to take place; the other point is left as the peripheral point of the resulting circle.
If more than two elements are selected, they are merged in pairs only if they have the same color, linetype, info text, and if there is no dimension specified at peripheral point where they might be merged.
-->(Meview_reset)-->--(CONFIRM)--->
This macro will reset the ME10v system defaults and redraw both the viewport and the screen menu.
Returns the point (vector) mirrored about a virtual mirror line. The angle between the X axis and this virtual mirror line is specified by number. As always, the current angle units are used.
,---------------<----------------,
| |
+->-(COPY)-------->--------------+
| |
+->-(DEL_OLD)----->--------------+
| |
| +->-(KEEP_READABLE)------+ | ,-|p1|->-|p2|-,
| | | | | |
-->(MIRROR)--->+--+->-(TWO_PTS)->|p1|-|p2|-+----+->---+-|pnt1|-->---+--->
| | | ^
| +->-(HORIZONTAL)->-|pnt|-+ |
| | | |
| +->-(VERTICAL)--->-|pnt|-+ |
| |
`->-(CENTER)----->---|pnt|-------'
MIRROR mirrors the elements across a given line or point. The line or point need not exist in the drawing.
With TWO_PTS, you give two points on the mirror line.
HORIZONTAL and VERTICAL mirror about horizontal and vertical mirror lines, respectively. The input is a point on the line.
CENTER is a point reflection, and has the same effect as a 180 degree rotation around the given point.
KEEP_READABLE option keeps texts readable after a mirror operation. This option forces the text angle after mirroring to lie between 0 to 90 or 270 to 360 degrees. In addition the texts will have their adjust points mirrored, and the slant will changes its sign.
Example: MODIFY (select) MIRROR KEEP_READABLE 0,0 1,1 mirrors the elements about the line through 0,0 and 1,1 keeping the text readable.
Returns the remainder of a division. For all X, X MOD Y = X-(X DIV Y)*Y.
+--------<-------------+
| |
-->(MODIFY)--+->---|select|----->---+-->
| |
+->---|MOVE|------>----+
| |
+->---|ROTATE|---->----+
| |
+->---|MIRROR|---->----+
| |
+->---|SCALE|----->----+
| |
+->---|SIMILAR|--->----+
| |
+->---|AFFINE|---->----+
| |
+->---(UNDO)------>----+
| |
+->---(COPY)------>----+
| |
+->---(DEL_OLD)--->----+
| |
+->-(repeat factor)->--+
| |
`->-(ASSIST)-----------'
MODIFY modifies elements with MOVE, ROTATE, MIRROR, SCALE, SIMILAR, or AFFINE. See MAPPING for a description of these transformations, including the syntax.
To use MODIFY, select elements, then subject them to one or more modifications. Or, specify a modification, then select elements one or more times. If you want only one selection and one modification, they can come in either order.
With DEL_OLD, the selected elements are transformed; with COPY, it is a copy that is transformed. The default is DEL_OLD.
UNDO helps you undo mistakes. With DEL_OLD, UNDO applies the reverse of the most recent transformation to the selected elements. With COPY, UNDO deletes the copies (1 or more, depending on the repeat factor) created by the most recent transformation. It is rarely possible to UNDO more than once.
You cannot use UNDO if you haven't selected or modified any elements.
The ASSIST qualifier switches on user assistance (COPILOT command). Additional graphical feedback and creation methods are then available. See the COPILOT command for more information.
The MODIFY button displays the dimension modification menu. The commands on this menu allow you to move existing dimensions, change extension lines, and to add and delete components to existing chain and datum dimensions.
+--------------------------------------------------+
| |
(MODIFY_DIM_LINES)--v-+------------------------------------------------+-->
| |
| +----------+---------------------+ |
| | | | |
+-(BREAK)-----v-|dim_id|-v-|from_pnt|-|to_pnt|-+-+
| |
| +-------------------------------+ |
| | | |
+-(STAGGERED))-v-|dim_id|-|pnt1|-|pnt2|-|pnt3|-+-+
| |
| |
| |
+-(RESET)--------|dim_id|---|selection|----------+
MODIFY_DIM_LINES allows you to put breaks into an existing dimension entity. Breaks can be put into dimension and extension lines. You identify the dimension to be modified (by picking the text of the dimension) and define the distance to be blanked by two points.
With option STAGGERED you can bend the extension line to make space for other elements on your drawing. After identifying the dimension (by it's value) pick points 1, 2, and 3 as shown below to move the line from its current 1 -> 2 position to the new 1 -> 3 position. The dimension line may be staggered only once.
| |
2 . . 3
staggered: | /
| /
1 ./
|
Radius, diameter, arc, angle, and chamfer dimensions cannot be staggered.
RESET restores the condition of the dimension without any breaks or staggered lines. Any modification of the dimension or its related geometry resets the staggers and breaks.
+<------------+
| |
(MODIFY_RELATIONSHIP)-----{element id}--+-->{parent}--+-->(CONFIRM)-->
| |
+-->{child}---+
{element id}
-->|element name|--+-------------------------------------------------------+-> | | +->(CURRENT)--------------------------------------------+ v | +->(SEL_OLD)--+->|revision string|->|version number|-+->+ | | +->|revision string|------------------>+ | | +->|version number|------------------->+
{parent}
--->(PARENT)------>(parent element id)-+->|quantity|------>
{child}
--->(CHILD )------>(child element id)-+->|quantity|------->
The MODIFY_RELATIONSHIP Command will modify the quantity of relationships between one element and any or all of its relatives.
Selecting the SEL_OLD option allows you to select an older (non-current) version of the element, the parent element or the child element.
By choosing PARENT you will modify the quanitity of relationships with the parent element. A specific parent or ALL may be specified.
By choosing CHILD you will modify the quanitity of relationships with the child element. A specific child or ALL children may be specified.
Quantity can be any positive number.
The value of quantity is considered the total number of links that the element should have to the parent/child element after the command has been executed. If the element already had a link or links to the parent/child, these links are ignored.
Permissions for modifying relationships are the same as relating elements.
If the user is modifying child relationships, the user's permission to modify the element is checked immediately. After all of the child relationships have been identified, the permission to modify the element is checked again.
As each child relationship is about to be modified , the two classes involved are checked to see if a defined relationship between them exists.
If the user is modifying parent relationships, the user's permission to modify the parent is checked immediately. If the user does not have permission to modify this parent, an error will be given.
As each parent relationship is about to be modified, the two classes involved are checked to see if a defined relationship between them exists. Then the permission to modify each parent is checked again.
Logical tables are used to display all the parents or children of the element. The logical tables can be modified as many times as the user would like. Only when the user has specified CONFIRM will any changes be made in the database.
If there is an unexpected system failure, all changes for the current execution of the MODIFY_RELATIONSHIP command will be rolled back.
+<---------------------------------+ | | | +<-------------+ | | | | | --->(MODIFY_USER)-+--|user login|--+--|priv num|--+--+->
MODIFY_USER creates a new user and/or sets the privilege of an existing user.
|user login| is the user's login name.
|priv num| is the new privilege number for the user for the specified product. Its range is 0 - 4, 0 implies no privilege. A default privilege of 4 will be set for the new user for all the products. Then, you will be prompted for the privilege settings for all the relevant products one by one.
An CoCreate/DMS privledge level of 1 is required to use this command.
While the commands are executing they keep a logical table "dms_su_table" filled with up-to-date information about the users' privilege level.
,--------<-------------,
| |
+->-(repeat factor)----+
| |
+->-(COPY)----->-------+
| |
+->-(DEL_OLD)-->-------+
|
-->(MOVE)--+--+->-(TWO_PTS)--+->-|begin point|--->---|end point|---------->
| | |
| `------->------'
|
+->-(HORIZONTAL)->--|horizontal distance|--------->------------>
|
|
+->-(VERTICAL)-->---|vertical distance|----------->------------>
|
| +--------<----------+
| | |
`->-(MULTIPLE)--->--|begin point|->--+->-|end point|-----+----->
MOVE moves the selected elements from one place to another.
With TWO_PTS you specify a begin and end point of the move.
With HORIZONTAL and VERTICAL, you specify how far the elements should be moved horizontally or vertically. The distance can also be negative, producing a move to the left (HORIZONTAL) or down (VERTICAL).
MULTIPLE is used to create multiple copies (with COPY). It is equivalent to a series of TWO_PTS, with the new begin point the same as the old end point.
Example: MODIFY (select) MOVE VERTICAL 10 moves the selected elements 10 units up.
+----------------------<--------------------------+
| |
(MOVE_DIMENSION)-+->-+->-------------+-|id_pnt|->-|move_pnt|----+--+-->
| | |
'->-(TEXT_ONLY)-' |
The MOVE_DIMENSION is used to move the dimension lines and text. If the option TEXT_ONLY is invoked, then the dimension lines are retained in their current position but the text is moved to a point defined by the user.
(MOVE_DIM_HIDDEN_ZERO_POINT)->-|dimension|->-|start_loc|--->
MOVE_DIM_HIDDEN_ZERO_POINT moves the location of the zero point of dimensions (dimension groups) created with HIDDEN_ZERO_POINT.
Note: This command is specific for ME10 Annotator.
(MOVE_DMS_FILE)-->|file name|-+-{element id}-+-->(AREA)--|area name|->(CONFIRM)->
| |
+--------------+
{element id}
-->|element name|--+-------------------------------------------------------+->
v |
+->(SEL_OLD)--+->|revision string|->|version number|-+->+
| |
+->|revision string|------------------>+
| |
+->|version number|------------------->+
The MOVE_DMS_FILE command is a maintenance command for the files in storage areas. Files can be moved from one storage area to another. For example, to move 'myfile':
MOVE_DMS_FILE 'myfile' 'myelement_c' 'new_area_name' CONFIRM
See REMOVE FILE for more detailed examples of files and elements.
-->(MOVE_ELEMENT)-+-----------+->{element id}->|new class|->(CONFIRM)--->
| |
+->(FORCE)->+
{element id}
-->|element name|--+-------------------------------------------------------+-> | | +->(CURRENT)--------------------------------------------+ v | +->(SEL_OLD)--+->|revision string|->|version number|-+->+ | | +->|revision string|------------------>+ | | +->|version number|------------------->+
This command moves ALL revisions and versions of an element from one class to another.
An element of the specified class is created.
The element name must be specified, and if the element's class allows revisioning and/or versioning, the revision string and/or the version number must also be entered whereby the last revision/version is prompted as the defaults.
If there are additional attributes describing an element of the given class, the user can insert the values for the selected attributes.
OWNER and GROUP of the element are automatically set, in accordance with the current user. The element gets the default permission mask if it's set, otherwise it defaults to '---', which means only specific users can access the element (see also description of access-rights).
A user must have write PRIV_1, PRIV_2 and ownership, or PRIV_3 and write permission to move an element.
All revisions and versions of an element will be moved to the new class, if possible.
If the user does NOT have permission to move all rev/ver of the element, NO element rev/vers will be moved and the command will abort.
If the user does NOT have permission to modify all parents of all rev/vers of this element, then NO rev/vers will be moved and the command will abort.
The owner of the element revs/vers will be changed to the user's login during the move.
An element can be moved to a new class, even though some or all of it's user-defined attributes, some or all revisions and/or versions, and some or all of its relationships to other elements may be lost.
As many of the user_defined attributes will be moved as can be matched.
Two user-defined attributes of different classes match if the attribute names match exactly and the data types are the same. Exceptions to this are moving an INT to a FLOAT, a CHAR to a VARCHAR, and a VARCHAR to a CHAR.
If the destination class does not have all the same user-defined attributes the data will simply be discarded. If, in the case of CHARs and VARCHARs, the length of the field is not the same, the string will be truncated when it is moved.
If the element has revisioning, versioning, releasing, or all three and the destination class does not have the corresponding configuration, then only the following element rev/vers will be moved and the rest will be deleted. (See charts below.)
SOURCE CLASS DESTINATION | Rv Vr Rl Rv Rl Vr Rl Rv Vr Rv Vr Rl CLASS +---------------------------------------------------------------+ Rv Vr Rl | ok 1 2 3 4 5 6 | +---------------------------------------------------------------+ Rv Rl | 7 ok 2 8 3 5 6 | Vr Rl | 9 10 ok 11 12 3 6 | Rv Vr | ok 1 2 ok 4 5 6 | +---------------------------------------------------------------+ Rv | 7 ok 2 7 ok 5 6 | Vr | 9 10 ok 9 10 ok 6 | Rl | 13 13 13 13 13 13 ok | +---------------------------------------------------------------+
2, 5, 9, 11 move ALL versions of the revision specified, setting revision strings and version numbers if needed. delete all remaining revisions and versions from old class
1, 4, 7, 8, 10, 12 move the given version of each revision, setting revision strings and version numbers if needed. delete all remaining revisions and versions from old class
6 move the specific rev/ver of the element, setting revision strings and version numbers if needed. delete all remaining revisions and versions from old class
If the element has relationships to other elements that are not allowed in the new class, these relationships will simply be removed. All other relationships to this element will be moved with the element.
If the FORCE option has not been set, the user will see any or all of the following warning messages before they are prompted to enter CONFIRM:
Warning: Some infos for
Warning: Some relationships to
Warning: Some revisions/versions of
Warning: The new class does not support releasing.
+----------<----------+ | | --(MOVE_TABLE)-|table_id|---+-|POINT|------|POINT|+-----(END)- | | +-(UPPER)+---+-(OF)+--+ | | | | | +-(LOWER)+ +-----+ | | | | +-(RIGHT)+ | | | | +-(LEFT)-+ | | | +---------------------+
This function allows you to move an existing table to a specific location on the screen.
Only those tables not secured by the program against move can be relocated.
--->(MOVE_TREE_NODE)-->{child node}-->{old parent node}-->{new parent node}--->
{child node}, {old parent node}, {new parent node}
---+->|name|-------------+---> | | +->(TOP)--------------+ | | +->(LAST)-------------+ | | +->(CURRENT)----------+ | | +->(BACK)-->|steps|---+
Move a child node from one parent node to the other in the current classification tree. All nodes must already be present in the current tree. After a successful move, a new link gets established between the new parent node and the child node whereas the link between the old parent node and the child node is deleted.
An existing node can be specified by typing its name or picking it from a table. Option TOP specifies the top node of the current tree, which also is the name of the current tree. Option CURRENT specifies the current node in the history of the node queries. Option LAST gives the last current node, BACK identifies a node queried earlier by given steps in the history.
A classification privilege of 2 is required to use this command.
When using this command, the view modification will be preserved after the associative documentation update (ADU).
When using this command, the view modification will be preserved after the associative documentation update (ADU).
When using this command, the view modification will be preserved after the associative documentation update (ADU).
The file "plotdefs" contains offsets, hard limits, color palette type supported, resolution for monochrome printing, resolution for color printing, image scaling device and image compression supported for all plotters and paper formats. This file is always read when you invoke a plot via the plot menu entry START PLOT. If the file "plotdefs" has changed during your session you have to enter the following line interactively:
LET Mustread_plotdefs (TRUE)
The following format is used (all sizes are in mm and resolution in dpi):
width_tolerance height_tolerance 'format name' 'plotter names' x_offset y_offset format_width format_height 'color palette type' 'monochrome resolution' 'color resolution' 'scaling' 'Compression support' ... ''
The width and height tolerances are subtracted from the format width and format height values respectively.
Color palette - 'mono,rgb3,rgb24'
If the device supports 3-plane RGB3 format, rgb3 will be included. If the device supports 24 bit per pixel direct encoding of image data, rgb24 will be included. Atleast one string 'mono' will be specified for monochrome device.
Monochrome Resolution - 'x,y'
Draft -x and Max -y resolution supported for monochrome printing.
Color Resolution - 'x,y'
Draft -x and Max -y resolution supported for color printing.
Scaling - 'me10/printer'
Scaling of images can either be done by me10 or by the device. In the former case the size of the file will be large and takes more time, but image qulity will be better.
me10 : Scaling of the image by ME10 itself. Printer : Scaling of the image by printer.
Compression - mode2 / mode0
Plot file can be compressed in TIFF Packbits Encoding by specifying mode2. For uncompressed plot files specify mode0.
mode2 : Compressed plot file mode0 : Uncompressed plot file
If the format width is smaller than the format height, the plot is rotated by 90 degrees.
---->|letter|---->+--------->--------+---->
^ v
| |
+<----|letter|<----+
| |
^ v
+<----|digit|<-----+
^ |
| v
+<------(_)<-------+
This describes the syntax of a macro name. Macros are defined by DEFINE, LET, and READ.
Names must begin with a letter; subsequent characters can be letters, numbers, or underscore (_). Included in letters are the standard ASCII letters as well as the extended ASCII characters from (CHR 161) through (CHR 254).
It is usually advisable to avoid macro names that are the same as keywords, which are the names known to the system on startup. However, if you really must, it is possible to redefine a keyword to a certain extent. Normally, you can type macro names in upper or lower case, or even mixed; keywords must be either upper or lower case. If you want to define a macro with the same letters as a keyword, you must avoid typing the macro name in one case. For example, 'LINE' and 'line' are always keywords, but 'Line' is available as a macro name. Once defined, the macro 'Line' can be invoked (and could have been defined) with any mixture of upper and lower case letters.
CoCreate/DMS queries may be either named or unnamed. Different commands are used to access these two types of queries. The following commands are for unnamed queries:
QUERY QUERY_AREAS QUERY_CLASSES QUERY_FILES SQL_QUERY STRUCTURE WHERE_USED
All of the other query commands work with named queries:
QUERY_ADD_CLASS QUERY_ADD_COLUMN QUERY_ADD_SELECT QUERY_ADD_SORT QUERY_COPY
QUERY_CREATE QUERY_CREATE_CLASSIFICATION QUERY_DELETE QUERY_DELETE_CLASS
QUERY_DELETE_COLUMN QUERY_DELETE_SELECT QUERY_DELETE_SORT QUERY_DESTINATION
QUERY_DIRECTION QUERY_EXECUTE QUERY_FILE_NAME QUERY_LEVELS QUERY_LIST
QUERY_MODIFY_CLASS QUERY_MODIFY_COLUMN QUERY_MODIFY_SELECT QUERY_MODIFY_SORT
QUERY_REFRESH QUERY_RENAME QUERY_SAVE QUERY_SELECT_TABLE_NAME QUERY_SET_SELECT
QUERY_SORT_TABLE_NAME QUERY_START_ELEMENT QUERY_START_REVISION QUERY_START_VERSION
QUERY_TABLE_NAME QUERY_TREE_CHILD_NODE QUERY_TREE_ELEMENTS QUERY_TREE_PARENT_NODE
QUERY_TYPE QUERY_USER_TABLE_NAME
An unnamed query lasts only for the duration of one commands. Each command has many options that allow you to specify all of the information for the query, including class names, element names, select conditions, sort order, and display options. If you want to repeat the query with minor changes, you must input the entire specification again.
In contrast, you must use several simple named query commands to specify a single query. The advantage of named queries is that after you have initially specified the query options, you may later make incremental changes to the specification without repeating the unchanged portion. For example, you may edit a named query to add a class, delete a display column, or modify a select condition.
You may create many named queries. Then, you may re-execute any query simply by entering its name, not its specification. There is a high degree of consistency between the various named query commands for elements, files, areas, classes, attributes and structures. For example, all of the named query commands support sorting options, where some of the corresponding unnamed query commands do not.
Named queries support more complex select conditions than unnamed queries. The conditions may include NOT. They may be grouped, using square brackets as parentheses. For more information about this capability, see QUERY_SET_SELECT.
Some named query commands operate on a single query (for example, QUERY_EXECUTE, QUERY_SAVE, QUERY_ADD_SORT, etc.) Other commands deal with the master list of queries (for example, QUERY_SAVE ALL, QUERY_DELETE ALL, QUERY_LIST etc.)
The named query commands do not support the "DETAIL_INFO" vertical output format (one attribute per line). The named query commands do not assist with selection of classes by restricting input to only PARTS classes.
Detailed differences for STRUCTURE / WHERE_USED:
The unnamed query commands allow you to specify a separate select condition for the starting class (or group of classes) and for each destination class (or group of classes). The named query commands allow only a single select condition for all classes. The named query commands allow only a single start element (without select conditions), not a starting class.
The unnamed query commands do not allow you to specify sort conditions and do not do any default sorting. The named query commands allows you to specify a sort condition. The condition is applied within each level of the hierarchy. To optimize performance, the named query commands do not do any default sorting.
Detailed differences for Files / Elements_to_files / Files_to_elements:
The unnamed query commands include three file query modes. The simple mode outputs all selected files, regardless of any related elements. The ELEMENTS_TO_FILES mode outputs all selected files. Following each file record, a record is output for each related element (if any) that matches the element select conditions. The FILES_TO_ELEMENTS mode outputs all selected elements. Following each element record, a record is output for each related file (if any) that matches the file select conditions.
The named FILES query provides two modes. The simple mode is equivalent to the simple QUERY_FILES command. You select the related elements mode by adding class names to the class list. The related elements mode outputs a single record for each related pair of files and elements.
The ELEMENTS_TO_FILES mode allows you to specify a separate select condition for the starting files and for each destination class (or group of classes). The FILES_TO_ELEMENTS mode allows you to specify a separate select condition for the starting class (or group of classes) and for the destination files. The named query commands allow only a single select condition for the query. The select condition may include file attributes and/or element attributes.
The unnamed query commands do not allow you to specify sort conditions and do not do any default sorting. The named FILES query allows you to specify a sort condition. The condition is applied within each level of the hierarchy. To optimize performance, the named query command does not do any default sorting.
By default, the ELEMENTS_TO_FILES option shows all revisions and versions of elements related to the selected files. By default, the named FILES query only displays current versions of elements. In either case, you may specify a select condition to see only the revisions and versions that you wish.
---->(NEW_SCREEN)---->
NEW_SCREEN redraws the entire screen.
--->(NODE_QUERY_PAGE)--+-------------+->|node name|-+--------+--+
| | | | |
+->(ELEMENTS)-+ +->(ADD)-+ |
v
+------------------------------------------+
|
| +<-------------------+
v | |
+->+->|query page name|-+-->(END)-->
| |
+------------------->+
Associate new query pages with a node name for the default node and element queries. Option ELEMENTS is used for element queries on a node otherwise node queries are assumed. Query pages to be associated must be present in the system. Any query page associated with a node name is secured against deletions.
A node name string must be given to associate the query pages. Option ADD associates more query pages to the node name otherwise all the previous query page associations with the node name are cleared and new associations get defined.
During a default query, pages for the node name are used to extract attribute names to query and their display characteristics. If no query pages are associated with the node name, query pages for the top node in the current tree are used, and if they too are not available, a special node name 'cnc_reserved_node' defined by the system is used for the query pages.
Any classificaition user can use this command.
Returns 1 if the argument equals 0, and otherwise returns 0.
The NOT modifier reverses the sense of the line type selection filter. Line types that were part of the filter are removed and types that were not part of the filter are added. The selection filter limits which drawing elements can be selected for dimensioning.
Returns the ordinal value of the first character in the argument string.
--->+---------->+--->+--------------------->(.)-------->|integer|--->+
| | | |
+--->(-)--->+ +--->|integer|--->+---------------------------->+
| |
+--->(.)--->+---------------->+
| |
+--->|integer|--->+
|
v
+<------------------------------------+
|
+------------------------------------------>
|
+-->(E)-->+->+---------->+--->|integer|---->
| | | |
+-->(L)-->+ +--->(+)--->+
| | | |
+-->(e)-->+ +--->(-)--->+
| |
+-->(l)-->+
integer
The format of a number is as shown. The possible exponent specifiers (E, L, e, or l) all have the same effect.
The exponent range supported is approximately -300 to 300. However, the system often computes the product of, say, point coordinates, which means -150 to 150 is a more realistic exponent range.
Data accuracy is approximately 12 decimal places in both environments.
The values entered via the numerical field appear in a display line above. To accept a value, pick the display line.
The OFFSET qualifier in the CREATE 1 menu is displayed only when COPILOT functionality is switched on (see COPILOT).
Certain construction geometry and drawing elements can be offset to other elements. First pick a command and then pick OFFSET. Pick the first and second elements to define the offset point and then pick the point.
All keywords marked with (OLD) are only for compatibility to older revisions and will be removed in future releases. Don't use these for new macros.
-->(OLE_LIST)--+-----(SCREEN)----------------------+---->
| |
'--+-----------+--|file specifier|--'
| |
+-(DEL_OLD)-+
| |
'-(APPEND)--'
OLE_LIST lists the information of OLE objects loaded in the current session. The information is shown in table, where each OLE object is in separate row. Columns are:
| OLE name | ME10 name of OLE object, specified on INSERT_OLE |
| Z-level | Z-level of OLE object |
| X-scale | X axis scale factor (can be modified with EDIT_OLE SCALE command) |
| Y-scale | Y axis scale factor (can be notified with EDIT_OLE SCALE command) |
| OLE Type | Type of insertion of OLE object: LINK, EMBEDDED or STATIC |
| Program ID | Program ID of OLE object |
| Class ID | Class ID of OLE object |
SCREEN sends the output to the text editor (see EDITOR). Otherwise, the output is sent to the file specified. With DEL_OLD, a file of the same name is overwritten without any error message. With APPEND, the OLE list goes to the end of the named file, if it exists; otherwise, a new one is created. With neither DEL_OLD or APPEND option, if a file of the same name is present in the specified path, error is reported.
---->(ON_ERROR)---->|string|---->
The string specified with the ON_ERROR function is used as input at the occurrence of the next error. Once used in this way, the string is discarded and ON_ERROR must be used again to re-enable this feature. To disable an active ON_ERROR, issue the ON_ERROR function with an empty argument string.
---->(OPEN_INFILE)---->|number|-->-+---------------+------>|filename|---->
| |
+->(NO_DELAY)->-+
OPEN_INFILE first closes any open file with the same id number and then opens the named file for reading by the READ_FILE function. Number is an integer in the range from 0 to 10 which is used for all subsequent references to this file.
NO_DELAY controls the behavior of the system if 'filename' is a named pipe. It affects the behavior of the OPEN_INFILE and READ_FILE functions.
Without NO_DELAY, an OPEN_INFILE of a named pipe will wait until another process opens the pipe for writing. After OPEN_INFILE returns, lines of text can be read from the pipe using the READ_FILE function. If a the READ_FILE returns 'END-OF-FILE', this means that the process writing into the pipe has closed its output.
With NO_DELAY, the OPEN_INFILE will return immediately. If there is data available in the pipe, subsequent calls to the READ_FILE function will return that data, but if READ_FILE returns 'END-OF-FILE' this only means that the pipe is currently empty. If data is later written into the pipe again, the READ_FILE function will again return that data.
---->(OPEN_INFILE)---->|number|---->|filename|---->
OPEN_INFILE first closes any open file with the same id number and then opens the named file for reading by the READ_FILE function. Number is an integer in the range from 0 to 10 which is used for all subsequent references to this file.
--->(OPEN_OUTFILE)--->|number|--->+------------------>+--->|filename|---->
| |
+---->(DEL_OLD)---->+
| |
+---->(APPEND)----->+
OPEN_OUTFILE first closes any open file with the same id number and then opens the named file for writing by the WRITE_FILE function. Number is an integer in the range from 0 to 10 which is used for all subsequent references to this file. The file may be a printer.
Returns 1 if one or both arguments are different from 0, otherwise returns 0.
,--------------------------------,
| |
v |
--->(ORIGIN)-+->|point or viewport number|----+-->+-->(ON)---,
| ^ | |
+->(ALL)-------------------------+ '-->(OFF)--+-->
| |
'------------------------------->'
ORIGIN turns the symbol for the input coordinate system origin on or off in the specified viewport(s) . If no viewport is specified the symbol is turned on or off in the current viewport. If the RULER is active in the specified viewport(s) , it is turned off.
-------------------
Plot and screen dump output can be sent either to the Windows Print Manager or to the Clipboard. When the Print Manager is selected, plot or screen dump data is generated using the current output parameters and then sent to the Print Manager for final output. Typically, the Print Manager handles spooling and selection of a printer/plotter device, as well as setting device-specific options. If the Print Manager requires additional input from you at print time, it will pop a dialog window on your display.
Sometimes it is desirable to be able to send a plot or screendump to a file rather than to a printer or plotter. The Print Manager allows you to route most print jobs to a file rather than to the printer/plotter itself. See your Windows documentation for details.
If the Clipboard is selected, the plot or screen dump image is stored in the Windows Clipboard, where it can be retrieved by other Windows applications. Only one image can be stored in the Clipboard at a time.
---->+-----+--->(SCREEN)-------+-------------------->+---->
| | | |
| +--->(PROMPT_LINE)--+ |
| |
+---->+------------------>+---->|file_name|---->+
| |
+---->(DEL_OLD)---->+
| |
+---->(APPEND)----->+
The output specification (named |output_spec| in the syntax diagrams) specifies the destination of the output produced by the command or function. This can be either SCREEN or a string naming a regular file, a device file, or a program.
SCREEN The output will be sent to the built-in screen editor for viewing.
All changes made to the text will be ignored.
PROMPT_LINE The output will be displayed line-by-line in the prompt line
without entering the built-in screen editor. This may be useful
if only a few lines of output are to be displayed.
|file_name| See FILE_NAME.
DEL_OLD This will first delete any already existing file named by |string|.
APPEND If the file named by |string| already exists, the new output will
be appended to the previous contents of that file. If the file
does not exist before, it will be newly created.
---->(OUTPUT_STRING)---->|string|---->
OUTPUT_STRING writes the contents of |string| to its output device. This can be used to enable soft keys in command line environments.
,--->(end pt)-------,
^ v
| |
->(OVERDRAW)-+---->---+-(begin pt)---+--->(pt on elem)---+--->(END)--->
v ^ ^ v
| | | |
`-ASSIST-' +-------(UNDO)<-----+
^ v
| |
'-------------------'
OVERDRAW lets you draw a series of connected lines and arcs (a biarc) over construction geometries. You first indicate the start point of the contour. The start point always must be at an intersection point where atleast one element is either a c_line or a c_circle. Only one start point is possible in a single OVERDRAW command. Next, a prompt to enter point on component will be displayed.
Then, identify either a c_line or a c_circle (say E1) for the contour to follow. This c_line or c_circle should pass through the start point. Feedback will be generated along the element.
To specify the end point of the line or arc, there are two possibilities. You can pick the end point either at intersection point on element E1, or on another element E3 which intersects with E1.
If the end point is at intersection point, an element either a line or an arc will be drawn from the start point to the end point and a prompt to enter point on component will be displayed. If the end point is specified by selecting another element E3, the closest intersection point between E1 and E3 will be taken as the end point. A line or arc according to the element type E1, is drawn from the start point to the end point. Feedback is generated from the end point along the element E3. A prompt for the end point is displayed. You can continue the contour by picking the end point either on an element or at an intersection point. The end point of the previous element is taken as the start point of the next element to be created. To come out of the OVERDRAW command say END.
With COPILOT on, the valid intersection points and the c-geometry are highlighted at every stage of the pick.
If DIC is also enabled, constraints are generated for the regular geometry created by OVERDRAW. All the lines would get collinear constraints with their corresponding c-lines. The arcs would get same size constraints as their corresponding c-circles.
UNDO will undo the earlier created geometries / selections in the current OVERDRAW command. The start point cannot be undone.