-->(UA_ANGLE_GRID)----|angle|---->
UA_ANGLE_GRID sets the angle increment used by COPILOT. The value is in the current angle units.
-->(UA_CENTER_CATCH_RANGE)----|value|---->
UA_CENTER_CATCH_RANGE specifies the portion of each line's length that COPILOT will treat as the center for catching. The value must be in the range 0.0 to 1.0. For example, a value of 0.2 specifies that one tenth the length of the line to either side of the center point may be considered as the center of the line for catching.
+-------------------||||||||||-------------------+
|<------ 0.4 ------>|< 0.2 >|<------ 0.4 ------>|
-->(UA_COPILOT)--+--(ON)---+-->
| |
+--(OFF)--+
UA_COPILOT turns COPILOT on or off. With COPILOT turned on, cursor information is displayed, incremental movement is available, and the size of geometry being constructed is displayed.
Refer to COPILOT for more information.
-->(UA_DESIGN_INTENT)--+--(ON)---+-->
| |
+--(OFF)--+
UA_DESIGN_INTENT turns Design Intent Capture on or off. With Design Intent Capture enabled, parametric constraints are generated during the creation of geometry. This command is only available with the Parametrics Module.
-->(UA_DIMENSION_FEEDBACK)--+--(ON)---+-->
| |
+--(OFF)--+
UA_DIMENSION_FEEDBACK turns on/off the display of feedback dimensions during geometry creation. This function is only meaningful when COPILOT is turned on.
-->(UA_DISTANCE_GRID)----|distance|---->
UA_DISTANCE_GRID sets the length increment used by COPILOT. The value is in the current length units.
-->(UA_GET_DESIGN_INTENT)---->
UA_GET_DESIGN_INTENT responds with the on/off status of Design Intent. The value returned is either:
0 -> Design Intent is not enabled 1 -> Design Intent is enabled
Design Intent may be enabled/disabled with the UA_DESIGN_INTENT command. UA_DESIGN_INTENT is only available with the Parametrics Module.
-->(UA_PERPENDICULAR_CATCH_RANGE)----|value|---->
UA_PERPENDICULAR_CATCH_RANGE specifies the portion of lines, circles, and arcs that COPILOT will treat as perpendicular for catching. The value must be in the range 0.0 to 1.0.
For example, a value of 0.2 specifies that one tenth the length of the arc to either side of a perpendicular point may be considered as the tangent of the arc for catching. For construction lines the value is with respect to the amount of the line displayed on the screen.
-->(UA_SET_CATCH_DELAY)----|delay|---->
UA_SET_CATCH_DELAY sets the amount of time that the cursor must be motionless before COPILOT catch information is displayed. A catch delay avoids feedback flashing and jumping when the cursor is moved across a complicated model. A catch delay will also improve performance with large models, because the cursor will not pause as it is being moved about the screen.
The delay is a positive number of seconds.
-->(UA_TANGENT_CATCH_RANGE)----|value|---->
UA_TANGENT_CATCH_RANGE specifies the portion of circles and arcs that COPILOT will treat as tangent for catching. The value must be in the range 0.0 to 1.0.
For example, a value of 0.2 specifies that one tenth the length of the arc to either side of a tangent point may be considered as the tangent of the arc for catching.
UNDO resumes the previous state. It can be used on certain commands and functions such as:
CONVERT_SPLINE
DELETE
DELETE_HATCH
EQUIDISTANCE
HATCH
LEADER_LINE
MODIFY
SPLINE
BSPLINE
STRETCH
DIM_CHAIN
DIM_DATUM_SHORT
DIM_DATUM_LONG
DIM_COORD
OVERDRAW
selection
NOTE:
DELETE
LEADER_LINE
selection
The following keywords are for internal use only, they should not be used by customers:
BUILD_NUMBER FEEDBACK_INDICATOR KEYWORD_STAT LIST_KEYWORDS LIST_MENUS MACRO_STAT MEMORY_STAT MENU_BUFFER PERF_MON_OFF PERF_MON_ON RETAIN_RASTER CONVERT_TO_HP_SYMBOLS
---->(UNITS)---->+----------------->+---->+---->(CM)------->+---->
| | | |
+---->|number|---->+ +---->(METERS)--->+
| |
+---->(KM)------->+
| |
+---->(MM)------->+
| |
+---->(UM)------->+
| |
+---->(INCHES)--->+
| |
+---->(FEET)----->+
| |
+---->(YARDS)---->+
| |
+---->(MILES)---->+
| |
+---->(MILS)----->+
| |
+---->(UINCHES)-->+
| |
+---->(DEG)------>+
| |
+---->(GRD)------>+
| |
+---->(RAD)------>+
UNITS specifies the current units of measure for distances and angles. With very few exceptions, commands and functions assume that all distance, angle, and coordinate input is in these units. The default is MM and DEG.
UM is micro-meters, UINCHES micro-inches, DEG degrees, GRD grads (sometimes called gradians), and RAD radians.
The optional number can be used to create new units. For example, UNITS 5 MM allows you to work in 5mm units.
UNITS does not change the size of any existing elements. It does not change the spacing of grid points or ruler ticks. It does change the unit distance in both the absolute and the input coordinate system; see CS for details.
---->(UNLOAD_MODULE)---->|string|---->
->(UNRELEASE)--->-{elem sel}->
{elem sel}
-+->|element name|--------------------->+-> | | | +<--------------------+ | v v | | +-+->(SELECT)--->|expr|-+-(SCREEN)---->+ | | +->(CONFIRM)-->+
|expr|
---->|att|-------+-------->+------>|value|------> | | +->(=)--->+ | | +->(<>)-->+ | | +->(>)--->+ | | +->(<)--->+ | | +->(>=)-->+ | | +->(<=)-->+
In order for the user to unrelease an element they must either be privilege 1, or be privilege 2 and the owner or have special permissions.
The status of the selected elements and of all files related to them is changed to unreleased. Unreleased elements and their related files may now be changed.
Constraints:
Only those elements may be unreleased, where:
Elements that are not released will be ignored without complaint by this command.
-->(UNRESERVE)---+->(FILE)->|file name|-------------------+->(CONFIRM)-->
| |
+->{element id}->+---------------------->+
| |
+->(FILE)->|file name|->+
{element id}
-->|element name|--+-------------------------------------------------------+-> v | +->(SEL_OLD)--+->|revision string|->|version number|-+->+ | | +->|revision string|------------------>+ | | +->|version number|------------------->+
Command to unreserve single files or all files which belong to an element and which have been reserved by a former DB_LOAD or CHECKOUT with option RESERVE and which should be marked as unreserved in the database without a further change.
security: to use this command you must be a privilege-1 user or you must be the person who has reserved the file and has additionally write permission for the element to which the file is related.
-->(UNSHARE_ACCURACY)---->|value|--->
UNSHARE_ACCURACY allows you to specify an accuracy range for matrix comparison in UNSHARE_BACK for parts which inadvertently became shared because of inaccuracies. The value must be in a range 0 to 0.000001.
,----------------------,
v ^
-->(UNSHARE_BACK)--+-->|part identifier|--+-->(CONFIRM)---->
| |
'-->(RECURSIVE)--------'
| |
'-->(MAP)--------------'
Due to accuracy problems in ME10/ME30 version 06.00 it could have happened that non-shared parts became shared after storing and loading.
A part identifier can be the following:
With option RECURSIVE, you may convert the whole parts subtree under the selected part.
With option MAP, you may convert also shared parts that have been modified (see condition 4 below).
To check and convert the whole drawing enter:
UNSHARE_BACK TOP RECURSIVE CONFIRM
Four conditions must be fulfilled to convert a shared part to a non-shared:
(1) The shared part is neither a detail nor an isometric part
(2) The parent part of the shared part is not shared
(3) There is only one instance of the shared part
(4) A shared part that has been modified (this means moved, rotated or scaled) as a part is not converted to a non-shared part. Only parts having the unit matrix (within an epsilon range) will be converted. The default value for this range is 0.000001.
If you want to select a different epsilon range please use the function UNSHARE_ACCURACY.
With option MAP, this condition is not evaluated but shared parts that have been modified are converted to a non-shared part by modifying the geometry with the shared part matrix.
,-----------------------------------,
v ^
---->(UNSHARE_PART)--+-->|name or pnt to identify part|--+-->
UNSHARE_PART takes a shared part and makes it unshared. See SHARED_PART.
Returns a string formed by replacing each lowercase character by its corresponding uppercase character.
-->(UPDATE_ELEMENT)--+->(INFOS)------->{elem sel}->+-{attribute list}---->
| |
| +--------------------->
|
+->(OWNER)------->{elem sel}->|owner name|---------->
|
+->(GROUP)------->{elem_sel}->|group name|---------->
|
+->(PERMISSIONS)->{elem_sel}->|permission mask|----->
|
+->(REVISION)---->{elem_sel}->|revision string|->--->
{elem sel}
{element id}
-->|element name|--+-------------------------------------------------------+-> v | +->(SEL_OLD)--+->|revision string|->|version number|-+->+ | | +->|revision string|------------------>+ | | +->|version number|------------------->+
{select}
+<--------------------+
v |
--+->(SELECT)--->|expr|-+-(SCREEN)-------->+->
| |
+->(CONFIRM)------>+
|expr|
---->|att|-------+-------->+------>|value|------> | | +->(=)--->+ | | +->(<>)-->+ | | +->(>)--->+ | | +->(<)--->+ | | +->(>=)-->+ | | +->(<=)-->+
{attribute list}
+<---------------------------------------+ v | +->|attribute name|-+->|attribute value|-+ | | ^ | +->(NULL)----------->+ v | -+----------------------------------------+-->(CONFIRM)-> | | | | +<-------------------+ | v | +->(PROMPT)-+->|attribute value|-+-------------------> | | +->(NULL)----------->+
element options:
Command to update the values of the user defined attributes and some system-defined attributes on each of the selected elements
Element selection:
An easy selection can be done by typing only the name. The newest revision and version of this element is selected.
With SELECT, you can specify a set of elements which should be considered. If you want to do an update on more than one element the update is done for each of the selected elements separately - if the attribute values should be updated (option INFOS) - if the revision should be changed (option REVISION). In all the other cases (OWNER, GROUP, PERMISSIONS) the update is done for ALL selected elements.
The selection is done by giving an attribute name, then saying what values that attribute will match.
For example,
SELECT 'Class' 'parts'
selects all elements of class 'parts'. The attribute name must be a string. The value is a string, except for the attributes VERSION and TOTAL where it is a number. For the items that are dates (CREATE_DATE, ARCHIVE_DATE, RELEASE_DATE), the value is expected in the form 'YY/MM/DD hh:mm:ss'.
All values can contain wildcards; thus
SELECT 'NAME' 'A*'
selects the elements whose names begin with 'A' .
SELECT also allows a relational operator between the attribute name and the value. Thus
SELECT 'CREATE_DATE' < '85/01/01'
selects the elements not created in 1985 or later, and
SELECT 'VERSION' > 3
selects elements with version numbers larger than 3. The operators can also be used with names; here '<' means 'earlier in an alphabetical ordering', etc.
You can use SELECT more than once. The resulting elements satisfy all of the selection criteria.
The attributes you can select on are strings, and must be one of the following:
NAME REVISION VERSION CREATE_DATE CLASS ARCHIVED_DATE ARCHIVE_LABEL RELEASE_DATE RELEASED_BY OWNER GROUP TOTAL
The option 'SCREEN' enters the built-in editor (see EDITOR) and allows you to verify the list of selected elements; any changes in the screen are ignored. With an unsuccessful exit (STOP/BREAK) from the editor you do not update anything.
security: see for each option separately
--->(UPDATE_SCHEMA)--|server node|--|database type|--|database env|--->
UPDATE_SCHEMA updates the schema of DMS databases prior to release 8.0.
The server node can be specified along with the port on the server at which the connection will be made if the desired port is not the default, 9898:
"local:9900"
The database type must be either ALLBASE or ORACLE.
The database env is the complete path the to database environment for an Allbase database. For an Oracle database the database env is the ORACLE_SID.
Example: Update an Allbase database:
LET Results (UPDATE_SCHEMA "myserver:9898" ALLBASE "/me_database/medb")
Update an Oracle database:
LET Results (UPDATE_SCHEMA "myserver:9898" ORACLE "PROD")
---->(UPDATE_SCREEN)---->
UPDATE_SCREEN displays any previous primitives that are not yet displayed due to device or driver buffering. It also forces an update of the status line and the menu. This function is only useful if executed from a macro or input file.
-->(UPDATE_STATISTICS)---->
This command will update ALLBASE system tables with statistical information about the other tables in the database. This command should be used after adding indexed attributes to classes with the DEFINE_CLASS or ADD_ATTRIBUTE commands. It should also be used when you want to determine how much space is left in each table.
--->(UPDATE_TREE_NODE)->{node}->{attribute list}--->
{node}
---+->|name|-------------+--->
| |
+->(TOP)--------------+
| |
+->(LAST)-------------+
| |
+->(CURRENT)----------+
| |
+->(BACK)-->|steps|---+
| |
+->{select condition}-+
{select condition}
--->(SELECT)-+---------------+-->(CONFIRM)--->
v |
+->{expression}-+
^ |
+--(AND)<-------+
^ |
+--(OR)<--------+
{expression}
-->|attribute name|->+-------->+->+->|value|->+----->
| | | |
+->(=)--->+ +->(NULL)-->+
| |
+->(<>)-->+
| |
+->(>)--->+
| |
+->(<)--->+
| |
+->(>=)-->+
| |
+->(<=)-->+
{attribute list}
+<----------------------------------------+
| |
---+->|attribute name|-+-->|attribute value|-+-->(CONFIRM)--->
| | |
| +-->(NULL)------------+
|
| +<-------------------+
| | |
+->(PROMPT)-+->|attribute value|-+---->
| |
+->(NULL)------------+
Update node attribute values in the current classification tree. System defined attributes NAME and TYPE can not be updated by the user.
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.
Multiple nodes can also be selected using SELECT option, and the selection can be based on the nodal attributes. Wildcards are allowed inside of 'value' if the comparison value is a string and comparison operator is '=' or '<>'. Wildcard '*' is used to match an aribtrary long search pattern and '?' matches exactly one arbitrary character.
Node attribute values can be set by giving the attribute name and the attribute value. With the PROMPT option, system prompts for the attribute values, one at a time. Initially, all attribute values are set to NULL.
A classification privilege of 2 is required to use this command.
---->(UPLOAD)---->|srcfile|---->|destfile|---->
UPLOAD transfers a file from the PC's local file system to the HP-UX file system. The transfer is an exact image of the file as it existed on the PC. 'destfile' is overwritten if it exists.
This command is only available if MEDISPLAYDRIVER has been set to pcterm.
ME10 has the possibility to store a URL in any form. Some examples of possible URLs (info text after 'URL: ') are as follows:
http://www.cocreate.com/home.htm http://www.hp.com ftp://ftp.mysite.org file:///d|/dir/install.html file:C:\users\joe\default.htm
It is possible to enter any string as a URL. These strings are not checked in ME10 for errors or availability. They are passed to browser as they are.
Local files
The file URL scheme is used to designate files accessible on a particular host computer. This scheme, unlike most other URL schemes, does not designate a resource that is universally accessible over the Internet.
A file URL takes the form:
file://<host>/<path>
where <host> is the fully qualified domain name of the system on which the <path> is accessible, and <path> is a hierarchical directory path of the form <directory>/<directory>/.../<name>.
The file URL scheme is unusual in that it does not specify an Internet protocol or access method for such files; as such, its utility in network protocols between hosts is limited.
Common browsers have different default ways of representing paths to files stored in the local file system. Netscape Communicator uses URLs like "file:///d|/dir/install.htm". Internet explorer uses standard Windows' notation like "c:\users\me10\default.html". Both browsers on the Windows platform accepts both notations.
Some browsers are able to distinguish between a local file and a URL if no standard prefix like "http:" or "file:" is given. Other browsers need prefixes. Users are encouraged to use standard addresses (resource locators) if they want to share their work with the other users.
URLs are stored as infotexts starting with characters 'URL: '. They are case-sensitive and no spaces before URL are allowed. There are many commands and functions handling infotexts. They can be used instead of specialized URL commands, functions and macros. The implementation is made similar to the LAYER implementation.
There can be specified several URLs per element. In this case the functions browse...url display the table of URLs and prompt the user to select one.
Elements get their URLs at creation time from CURRENT URLs. The CURRENT URLs are current infotexts starting with prefix URL: .
---->(USE_MULTILINE_HATCH)---->+----->(ON)------->+--->
| |
'----->(OFF)------>'
The function USE_MULTILINE_HATCH allows you to select two different hatching processes for hatches with a distance of 0. If USE_MULTILINE_HATCH is ON, polygons having inner contours are hatched using a line-fill process. This has the advantage that multiple-intersecting inner contours are hatched as expected. If USE_MULTILINE_HATCH is OFF, the system uses the normal polygon- fill to fill the hatch.
The default is ON.
---->(USE_NEW_FILE_FEATURES)---->+--->(ON)---->+---->
| |
+--->(OFF)--->+
The USE_NEW_FILE_FEATURES function enables or disables the use of new file features that came with ME10 version 07.10.
The new file features are:
'=' ',' '+' ';' ' '
in filenames
Since version 10.50, this switch is set to ON, by default.
Returns the token whose ASCII representation is given by string. The reverse function of VAL is STR.
To allow VARIO filing compatibility, two commands are available:
V_LOAD to load VARIO files V_DRAW to create variations of the loaded VARIO files
---->(V_LOAD)---->|file-name|---->
The V_LOAD command loads MI files created with VARIO. You have to be in the directory where your VARIO MI-file is.
---->(V_DRAW)---->
If you have loaded a VARIO MI file you can see which parameters your drawing has. You can modify them with the LET command, e.g. LET D1 100.
After you have modified all parameters you can create a varation with the V_DRAW command.
-->(VERSION)-->
VERSION displays version information.
-->(VIEW)----------+->|part name|-----+-->
| ^
|--->|point|------>|
| |
|--->(PARENT)----->|
| |
'----->(TOP)-------'
VIEW causes the selected part to be viewed in the current viewport. You can select the part in several ways -- by entering its name, by identifying its box if it is boxed, by identifying any element in it (except a part) if it is visible, or by entering PARENT or TOP.
The name of the viewed part is shown in the upper-left corner of each viewport.
-->(View_elem_url)------->(point selection)-->
-->(View_part_url)-----+->|point|----->+----->
| |
+--|part name|->+
-->(View_current_url)------->
-->(View_global_url)------->
These commands show a table with all the URLs for the specified object.
A click to an URL in the list puts the tokens representing URL in the input queue. It has the same effect as typing URL in the input line (like ('http://www.cocreate.com') ). This is used as part of other commands.
---->(VIEWPORT_CATCH)---->+------>(ON)----->+---->
| |
`------>(OFF)---->'
Default: ON
In the default mode (ON), viewports, menus, and tables catch to the positions of other viewports, menus, and tables when they are created, resized, or moved. The catch range is 8 pixels. Set VIEWPORT_CATCH OFF to disable this behavior.