This CoCreate/DMS menu selection brings back the ME10/ME10v/ME30 menu that was active when you entered CoCreate/DMS.
-->(BACKUP)->|logfile1|-+->(CONFIRM)-->+->|destination|---> | | +->|logfile2|->+
The database and all related files are copied to 'destination', where 'destination' is the name of a destination file (e.g. device file) where all backed up information is held. The 'destination' must be an absolute path. If the destination file already exists it is overwritten.
No other user may access the database during the BACKUP. To prevent other
CoCreate/DMS clients from connecting to the server during backup, a lock file is
created on the server named
If the database has been created with the dual logging option, both logfiles must be specified for a complete backup.
The logfiles have to be specified with an absolute path. For ease of use, the menu button BACKUP uses the macro variables Sys_db_logfile1 and Sys_db_logfile2 for the two logfile names. These variables should be set in the customize file, along with the Sys_server_node and Sys_database macros.
BACKUP writes its output in the "cpio -c" format. The files are stored on the destination with their absolute path name. To reload a backup copy (e.g. because of a disk crash), you must be the root user. Once logged in as root use the appropriate command listed below:
'tcio -iv destination | cpio -icuvd'
(if you have stored your backup copy on a cartridge tape)
'cpio -icuvd < destination'
(if you have stored your backup copy on another medium than a
cartridge tape)
(refer to the corresponding Unix manuals for complete descriptions of cpio and tcio)
With these HP-UX commands, the database and all related files are restored to their original locations. With the cpio -u option, all files will be restored, even those which are newer than the backup files. This means the whole database on your server and all files in all storage areas are overwritten by the backup copies. If any of the files in the database directory need to be restored, restore all the files to keep the database files consistent with one another.
If you only want to reload one file (e.g. one corrupt drawing file) from the backup, look for its physical name (attribute PHYS_NAME) in the data base and for the storage path of the storage area on which the file resides. Specify these parameters in the form '/storage_path/phys_name' as parameter 'pattern' in the sequence
'cpio -icuvd pattern < destination'
If the destination file is a device file you have to specify the raw device file name (e.g. /dev/rct/c1).
security: command can be invoked by level 1 users only and only if no other users are connected. You have be the root user to restore the files.
The BACKUP menu allows the user to do database backups, archive elements and restore elements.
---->(BEEP)---->
BEEP produces an audible tone.
---->(BEGIN_WORK)---->
BEGIN_WORK starts a database transaction. All database operations performed between a BEGIN_WORK and COMMIT_WORK are considered a single transaction to the database. Local files which are modified by DMS commands (like CHECKIN and CHECKOUT) will not be permanently removed from the HP-UX file system until the transaction is ended with COMMIT_WORK.
If a transaction is aborted, all files altered by DMS commands will be returned to their original states. Files altered by HP-UX commands, or by ME 10 file commands (like COPY_FILE, PURGE_FILE, etc.) will not be returned to their original state.
---->(BINDTEXTDOMAIN)---->|domain|---->|dir_name|---->
BINDTEXTDOMAIN function binds the given domain to a file in the specified directory.
It is important to remember that relative path names for the 'dir_name' parameter can be trouble. Since the path is always computed relative to the current directory different results will be achieved when ME10 executes a CURRENT_DIRECTORY command. Relative paths should always be avoided to avoid dependencies and unreliabilities.
Standard place for locale drectory in ME10 is MEDIR + "/locale".
-->(BITMAP_TO_FILE)--->,
|
,<------------<-----'
|
`-+------------------+->-+---------------------------->+->-+-------------->+--->|destination|-->
| | | | | |
+-->(TIFF)-------->+ +-->(PORT)------>|pnt|------->+ +-->(DEL_OLD)-->+
| | | |
+-->(JPEG)-------->+ `-->(BOX)-->|pnt1|-->|pnt2|-->'
| |
+-->(BMP)--------->+
| |
`-->(STARBASE)---->'
BITMAP_TO_FILE writes the contents of the graphics screen to the specified file.
Examples: To send the complete screen to a pipe, where the pcltrans command is invoked, enter: BITMAP_TO_FILE STARBASE '|pcltrans -I -d7.5 -h10.0 -C -a4 -g1.85 > /dev/rlp'
To send the contents of the box 0,0 150,300 to a regular JPEG file, enter: BITMAP_TO_FILE JPEG BOX 0,0 150,300 '/tmp/bitmap_file'
The BOM menu allow the user to access the Bill of Materials Application of CoCreate/DMS. BOM allows the user to create, format, and edit a bill of materials from the data in the database.
-->(BOM_ADD_PART)-->+------{parent part}---------->+--->+
| | |
+-(STRUCTURE_NUMBER)-|string|->+ |
|
+<----------<--------------<--------+
|
+<----------<--------------<------------+
| |
+------{child part}----------->+-|qty|->+->
| |
+-(STRUCTURE_NUMBER)-|string|->+
{child part} {parent part}
-->|part name|->+------------------------------------>+->
| |
+-(SEL_OLD)->+-|old rev|--|old vers|->+
| |
+-|old revision string|->+
| |
+-|old version number|-->+
Add qty of child part to a parent assembly. Parent and/or child part may be specified in two ways: by name or by structure number.
Specifying parent and child parts by name may be done at any time, without opening a part with the BOM_OPEN command. The current revision and version of the part with the specified name is selected unless the SEL_OLD option is used, in which case a specific revision and/or version of the part is selected. If the named part is the member of a class which does not have revisioning or versioning, the SEL_OLD option has no meaning.
Specifying the parent or child part by structure number requires that a part structure be loaded into the BOM Editor with the BOM_OPEN command and that the specified structure numbers exist in the parts structure. This is because structure numbers only have meaning within a part structure. When a part is identified by structure number the specific revision and version of the part already in the part structure is selected. This differs from parts identified by name where the current revision and version of the part is selected, unless the SEL_OLD option is used.
Any child part elements that added to the parent part will have their 'in-use' flags set on the database for data consistency between the BOM Editor and the database. The parent part becomes the implied parent for further part additions. When the BOM Editor is in assembly mode the open assembly is always the implied parent for BOM_ADD_PART. The assembly mode is activated with the BOM_ASSEMBLY_MODE command.
-->(BOM_ASSEMBLY_MODE)->+--(ON)--->+--->
| |
+--(OFF)-->+
Activate or deactivate the Bill Of Materials Editor assembly mode. The editor assembly mode differs from the default full tree mode in several respects. When a part is opened with the BOM_OPEN command only the parent part and its immediate child parts are queried from the database, providing better performance over the full tree mode, where the entire part tree is queried. The single level that is shown in the editor table alse provides a simpler picture of the part, similar to that shown in the full tree mode when BOM_DISPLAY_DEPTH is used with a depth of one (1). The operation of the editing commands: BOM_ADD_PART, BOM_REMOVE_PART, and BOM_SET_QUANTITY also change. The parent part of the open assembly is the implied parent for all of the edit commands, simplifying the editing process.
Default on powerup: OFF
-->(BOM_CLOSE)-->
Close all part trees or assemblies currently open in the BOM Module and clear the 'in-use' flag for all elements present in the BOM Module.
-->(BOM_DISPLAY_DEPTH)->+--|depth|->+-->
| |
+--(ALL)--->+
Limit the depth of the displayed part structure in the BOM Editor to depth or show the entire structure by selecting ALL.
This command may be combined with the BOM_NAME_INDENT, BOM_SHOW and BOM_FLATTEN functions to produce different reports.
Default on powerup: ALL
-->(BOM_EDITOR_DISPLAY_TABLE)---|display table name|----->
Declare the display table created in the configuration macro file 'bom_setup' to the BOM Editor application to use as the BOM Editor display table.
-->(BOM_EDITOR_FORMAT)->+--(FLAT)----->+-->
| |
+--(EXPLODED)->+
| |
+--(INDENTED)->+
Change the display format of the part structure in the BOM Editor.
The FLAT option causes the display of the BOM Editor to contain a single line for each unique displayed part together with the total quantity of the part in the structure.
The EXPLODED option causes the display of the BOM Editor to contain an exploded view of the part structure. In the exploded view the full part hierarchy is visible.
The INDENTED option causes the display of the BOM Editor to contain an exploded view of the part structure. The column of the Editor that displays the attribute NAME will be indented for each level that a part is in the part hierarchy. The amount of indent is selectable with the BOM_NAME_INDENT command.
Default on powerup: INDENTED
-->(BOM_EDITOR_QUERY_PAGE)-+-------->+->+-------------------->+--(END)-->
| | | |
+--(ADD)->+ +<-|query-page-name|<-+
Clear and unsecure the existing BOM Editor query-pages and optionally add new query-pages or append new query-pages to the existing ones. New pages are secured against deletion until they are removed from the BOM Editor.
EXAMPLES:
BOM_EDITOR_QUERY_PAGE END
Removes the existing query-pages.
BOM_EDITOR_QUERY_PAGE 'page1' 'page2' END
Removes existing query-pages and add two new query-pages, named 'page1' and 'page2' as new pages. The query pages 'page1' and 'page2' must have been previously created with the MAKE_QUERY_PAGE command.
BOM_EDITOR_QUERY_PAGE ADD 'page1' 'page2' END
Keep the existing query-pages and append two new query-pages, named 'page1' and 'page2', as new pages. The query pages 'page1' and 'page2' must have been previously created with the MAKE_QUERY_PAGE command.
This command can only be run when the BOM Editor is empty (ie. before a part has been opened with BOM_OPEN or after executing BOM_CLOSE).
-->(BOM_FLATTEN)->+--(ON)-->+--->
| |
+--(OFF)->+
Turns the flatten status of the BOM Editor on or off. Flattening causes the display of the BOM Editor to contain a single entry for each displayed part together with the total quantity of the part in the assembly or part tree.
This command may be combined with the BOM_NAME_INDENT, BOM_SHOW and BOM_DISPLAY_DEPTH functions to produce different reports.
Default on powerup: OFF
-->(BOM_FORMATTER_OPEN)-->{element id}-->(CONFIRM)
{part}
-->|part name|->+------------------------------------>+->
| |
+-(SEL_OLD)->+-|old rev|--|old vers|->+
| |
+-|old revision string|->+
| |
+-|old version number|-->+
Open the database part tree begining with the element id. Marks the tree IN USE until the user closes the part tree with BOM_CLOSE. The part tree is NOT displayed in the BOM editor display table.
-->(BOM_FORMATTER_QUERY_PAGE)-+-------->+->+-------------------->+--(END)-->
| | | |
+--(ADD)->+ +<-|query-page-name|<-+
Clear and unsecure the existing BOM Formatter query-pages and optionally add new query-pages or append new query-pages to the existing ones. New pages are secured against deletion until they are removed from the BOM Formatter.
EXAMPLES:
BOM_FORMATTER_QUERY_PAGE END
Removes the existing query-pages.
BOM_FORMATTER_QUERY_PAGE 'page1' 'page2' END
Removes existing query-pages and add two new query-pages, named 'page1' and 'page2' as new pages. The query pages 'page1' and 'page2' must have been previously created with the MAKE_QUERY_PAGE command.
BOM_FORMATTER_QUERY_PAGE ADD 'page1' 'page2' END
Keep the existing query-pages and append two new query-pages, named 'page1' and 'page2', as new pages. The query pages 'page1' and 'page2' must have been previously created with the MAKE_QUERY_PAGE command.
This command can only be run when the BOM Editor is empty (ie. before a part has been opened with BOM_OPEN or after executing BOM_CLOSE).
--->-(BOM_HIGHLIGHT_PART)-+---|Part Name|---+---(END)-->
| |
+-|Point on Part|-+
BOM_HIGHLIGHT_PART highlights all ME 10 parts which match the 'Part Name', or the part selected by the picked point. During the BOM_HIGHLIGHT_PART command, the status line shows the name of the selected part, and the ME 10 current part is set to match the selected part. If more than one part is selected (by giving a part name), all parts with that name will be highlighted, and the current part will be set to one of the parts of that name.
-->(BOM_NAME_INDENT)-+-|indent|->+->
| |
+--(ON)---->+
| |
+--(OFF)--->+
Control the indenting of part names in the BOM Editor and Formatter. Indent is not provided in the BOM Editor when BOM_FLATTEN ON or BOM_EDITOR_FORMAT FLAT are in effect. Indent is not available from the BOM Formatter if the BOM_QUERY FLAT option is used. Name indenting in the Editor is activated with the ON option and turned off with the OFF option. Name indenting in the Formatter is controlled by the FLAT, INDENTED, and EXPLODED options to BOM_QUERY. The number of indent spaces for both the Formatter and the editor are set by entering a new indent value as a number greater than or equal to one (1) and less than or equal to twenty (20).
This command may be combined with the BOM_FLATTEN, BOM_SHOW, BOM_EDITOR_FORMAT and BOM_DISPLAY_DEPTH functions to produce different reports.
Default on powerup: 2 space per level, ON
-->(BOM_OPEN)---{part}----(CONFIRM)------->
{part}
-->|part name|->+------------------------------------>+->
| |
+-(SEL_OLD)->+-|old rev|--|old vers|->+
| |
+-|old revision string|->+
| |
+-|old version number|-->+
Load a part tree or single-level assembly into the BOM Editor. A part must be loaded into the BOM Editor before the STRUCTURE_NUMBER option in editing commands will be accepted. The parts that are read into the BOM Editor will have their 'in-use' flags set on the database. This provides some security against concurrent changes by other users to the parts that have been loaded.
-->(BOM_PARTS_ONLY)->+--(ON)--->+--->
| |
+--(OFF)-->+
Configure the BOM Editor to allow parts only to be displayed and part relationships edited or to allow all relationships in the structure to be displayed and edited. This command can only be run when the BOM Editor is empty (ie. before a part has been opened or after executing BOM_CLOSE).
Default on powerup: ON
-->(BOM_QUERY)-+--------------+->|Destination LTAB|--->+
| | |
+-(USE_TITLES)-+ |
|
+----------------------<-----------------------+
|
+------->--------------+--+------->-----------+--+-->(FLAT)----+-->
| | | | | |
+->(DEPTH)->+->(depth)-+ +--->(LEAF_PARTS)---+ +->(EXPLODED)-+
| | | | | |
+-->(ALL)--+ +->(ASSEMBLY_PARTS)-+ +->(INDENTED)-+
| |
+------>(ALL)-------+
BOM_QUERY copies the 'current' element and its children from the BOM to the logical table given as the destination LTAB. Data from the BOM is written to the logical table based on the union of all the query sets defined to the formatter through the BOM_FORMATTER_QUERY_PAGE command. If a database attribute is in one of the formatter query sets, the value for that attribute will be written to the logical table. To create an empty column, use a non-existent attribute name in the query page.
If the USE_TITLES qualifier is given, then the attributes will be written to the destination logical table based on the logical table titles. For instance, if the first title string in the logical table was NAME, then the value of the NAME database attributes would be written to the first column of the logical table. Without the TITLE qualifier, all attributes currently used by either the BOM editor or the BOM formatter will be written to the logical table, with the attribute name in the logical table title for that column.
If no depth is given, then all children of the specified part will be loaded. If the part type (LEAF_PARTS or ASSEMBLY_PARTS) is given, then only parts of that type will be displayed. If no part type is given, then all children of part name which are 'parts' will be extracted. (An element is a 'part' if it is stored in a 'parts' class).
EXPLODED lists the complete parts list with all its part names as left justified strings. If the title 'STRUCTURE NUMBER' is listed in the output table, then a structure number will be output to indicate the part's position in the tree. INDENTED implies an exploded parts list with the parts list hierarchy illustrated by leading spaces in the part names. INDENTED may also include the structure numbers if the string 'POSITION' is one of the titles in the source table.
BOM_QUERY first checks if the BOM_FORMATTER_OPEN command has been used to open a part tree. If it has, then that tree is used. If BOM_FORMATTER_OPEN has not been used, then it checks if the BOM_OPEN command has opened a part tree and uses that tree. If neither BOM_FORMATTER_OPEN nor BOM_OPEN have been used, an error message is reported and BOM_QUERY aborts.
-->(BOM_REFRESH_EDITOR)->
Cause the editor to refresh. This command is useful if query configuration is changed interactively and the user desires to see the new configuration displayed.
+<---------------<---------------<--------------+
| |
-->(BOM_REMOVE_PART)->+---{parent part}---{child part}--->+->+-|qty|->+-->
| | | |
+----(STRUCTURE_NUMBER)----|sn|---->+ +-(ALL)->+
{child part} {parent part}
-->|part name|->+------------------------------------>+->
| |
+-(SEL_OLD)->+-|old rev|--|old vers|->+
| |
+-|old revision string|->+
| |
+-|old version number|-->+
Remove qty or all of part from parent part. If qty exceeds the actual quantity of part in parent part, quantity removed defaults to ALL. The parent and part may be specified directly by name, or implicitly by structure number if a part structure has been loaded into the BOM Editor with the BOM_OPEN command. When the BOM Editor is in assembly mode, using BOM_ASSEMBLY_MODE ON, the opened assembly is always the implied parent for BOM_REMOVE_PART.
-->(BOM_SET_QUANTITY)-->+---{parent part}----{child part}-->+--|new qty|--->
| |
+----(STRUCTURE_NUMBER)----|sn|---->+
{child part} {parent part}
-->|part name|->+------------------------------------>+->
| |
+-(SEL_OLD)->+-|old rev|--|old vers|->+
| |
+-|old revision string|->+
| |
+-|old version number|-->+
Change the quantity of a child part in a parent part to new qty. If new qty is equal to or less than zero, all relationships between part and parent part are removed. The parent and part may be specified directly by name, or implicitly by structure number if a part structure has been loaded into the BOM Editor with the BOM_OPEN command. When the BOM Editor is in assembly mode, set with BOM_ASSEMBLY_MODE ON, the top part is always the implied parent for BOM_SET_QUANTITY.
-->(BOM_SHOW)->+--(ALL)------------>+--->
| |
+--(LEAF_PARTS)----->+
| |
+--(ASSEMBLY_PARTS)->+
Select parts that are visible in the BOM Editor based on whether they contain subparts or not. All parts are displayed if the ALL option is selected. If display of only leaf parts (those with no child parts) is desired, use the LEAF_PARTS option. If display of only assembly parts (those that contain child parts) is desired, use the ASSEMBLY_PARTS option.
This command may be combined with the BOM_FLATTEN, BOM_NAME_INDENT and BOM_DISPLAY_DEPTH functions to produce different reports.
Default on powerup: ALL
-->(BROWSE_URL)------->|URL|-->
Shows in the browser the information contained in given URL.
These macros start or switch to the browser and show the contents of URL. If there are several URLs specified for the object, a table is displayed. The user then clicks one of URLs that is to be shown in the browser.
,------------------------------,
| |
v |
->(BSPLINE)-+->----------------------------+-->(END)---->
| ^
| |
+->|interpolation point|------+
| |
+->(CLOSED)->------------------+
| |
+->(OPEN)->--------------------+
| |
+->(TANGENT)->-+-|angle|->-----+
| | |
| +-|data pnt|->----+
| |
|->(APPEND)->--|data pnt|------+
| |
+->(ORDER)->---|number|->------+
| |
+->(UNDO)->--------------------+
|
`->(CONTROL_POINTS)->---------{1}
,------------------------------,
v |
{1}---------+->----------------------------+-->(END)---->
| ^
| |
+->|control point|-------------+
| |
+->(CLOSED)->------------------+
| |
+->(OPEN)->--------------------+
| |
+->(KNOT_VECTOR)->------{2}----+
| |
+->(ORDER)->---|number|->------+
| |
`->(UNDO)->--------------------'
,------------------------------,
v |
{2}---------+->|knot_value|----------------+--->
| ^
`->|curve point|---------------'
The BSPLINE command creates a B-spline curve.
When you pick or enter a set of points, the system interpolates these points and draws a spline curve through them. The options to this command are:
CLOSED:
The begin and end points of the curve are located in the same place and have a smooth transition at the common point. When you use this option, you do not need to specify the last point.
OPEN:
Use this option to create an open spline. The begin and end points of the curve are located in the same place. This is the default.
TANGENT:
APPEND:
CONTROL_POINTS:
Use this option when you do not want to interpolate a given set of points but to produce a rough sketch of the spline. The data points or "control points" affect the spline similar to the attraction of a magnet. The frame enclosing the spline is called the "control polygon".
KNOT_VECTOR:
# knot_vector = # control points + order # control points >= # order # interpolation points + # tangency conditions >= # order
where "#" is a number or quantity. The number of control points must be greater or equal to the order of the spline. For example, you cannot specify a spline of order 3 with only 2 control points. If you want to use this option, you must specify the order and the control points (using the option CONTROL_POINTS) of the spline first.
With this option, it is also possible to add curve points to the spline: all coordinates entered after this keyword are interpreted as curve points.
ORDER:
Use this option to specify the order (degree of curve plus 1) of the spline. Increasing the order makes the curve smoother. The default value is 4, possible values are 3 to 10.
,-------<------------,
| |
v |
->(BSPL_ADD_C_PNT)--+--|selection|---+--|pnt_1|--|pnt_2|--+--(END)--+--(END)--->
^ | | |
| `----(UNDO)----------' |
| |
`-----------------------------------------------`
Use this option to add a new control point between two neighboring control points. You must first identify the spline, pick the middle of two neighboring control points (pnt_1) and then indicate the position of the new point (pnt_2). If you have created a spline via interpolation (see BSPLINE) and add a control point, the interpolation points are kept (to retain associated dimensions) but are no longer valid interpolation points. If you do a modification via interpolation (see BSPL_MOVE_I_PNT) the whole shape may change. UNDO recovers the last modification, while CANCEL recovers all modifications.
,-------<------------,
| |
v |
->(BSPL_ADD_I_PNT)--+--|selection|---+--|pnt_1|--|pnt_2|--+--(END)--+--(END)--->
^ | | |
| `----(UNDO)----------' |
| |
`-----------------------------------------------`
Use this option to add curve points on the spline. You pick a point between two existing curve points (pnt_1) and the new position (pnt_2). The shape of the spline changes. UNDO recovers the last modification, while CANCEL recovers all modifications.
,-------<--------,
| |
v |
->(BSPL_DEL_C_PNT)--+--|selection|---+---|data_pnt|---+-----(END)--+--(END)--->
^ | ^ |
| | | |
| `-->(UNDO)------>' |
| |
`----------------------------------------------`
Use this option to delete control points from the spline. The shape of the spline changes. If you have created a spline via interpolation (see BSPLINE) and delete a control point, the interpolation points are kept (to retain associated dimensions) but are no longer valid interpolation points. If you do a modification via interpolation (see BSPL_MOVE_I_PNT) the whole shape may change. UNDO recovers the last modification, while CANCEL recovers all modifications.
,-------<--------,
| |
v |
->(BSPL_DEL_I_PNT)--+--|selection|---+---|data_pnt|---+-----(END)--+--(END)--->
^ | ^ |
| | | |
| `-->(UNDO)------>' |
| |
`----------------------------------------------`
Use this option to delete curve points from the spline. The shape of the spline changes. UNDO recovers the last modification, while CANCEL recovers all modifications.
,-------<--------,
| |
v |
->(BSPL_DEL_TANGENT)-----+--|selection|---+---|data_pnt|---+--(END)--+--(END)-->
^ | ^ |
| | | |
| `-->(UNDO)------>' |
| |
`-------------------------------------------`
Use this option to delete tangents at certain curve points. The spline shape changes. UNDO recovers the last modification, while CANCEL recovers all modifications.
,---------------------------------------------,
| ,---------------------, |
| | | |
v v | |
->(BSPL_MOVE_C_PNT)-+-|selection|--+---|pnt 1|--|pnt 2|--+--(END)-+-(END)--->
| ^
| |
+---(POSITION)->------+
| |
`---(UNDO)->----------`
Use this command to change the position of a control point. First identify the spline and then pick a control point (pnt 1) followed by the new position of the control point (pnt 2). UNDO recovers the last modification, while CANCEL recovers all modifications.
,------------------------------------------------,
| ,------------------------, |
| | | |
v v | |
->(BSPL_MOVE_I_PNT)-+-|selection|--+---|pnt 1|--+-|pnt 2|---+--(END)-+-(END)--->
| | ^
| +-|angle|->-|
| |
+---(POSITION)--->-------+
| |
+---(TANGENT)->----------+
| |
`---(UNDO)->-------------`
Use this command to modify a spline. To modify a spline, first identify the spline, and then specify one of the following options:
POSITION:
The first point (pnt 1) indicates the old position, the second point (pnt 2) is the new position of the spline.
TANGENT:
Use this option to change the tangent or slope at the specified point pnt 1. The tangent is determined by the direction vector of pnt 1 to pnt 2 or by a number (angle).
UNDO:
Undo will recovers the last modification, while CANCEL recovers all modifications. With this command, you can pick interpolation points only. The whole spline is re-computed, that is, the shape may change globally (rippling effect). The tension or strain of the spline is minimal.
,---------------------------------------------,
| ,---------------------, |
| | | |
v v | |
->(BSPL_MOVE_PNT)-+-|selection|--+---|pnt 1|--|pnt 2|--+--(END)-+-(END)--->
| ^
| |
+---(POSITION)->------+
| |
+---(TANGENT)->-------+
| |
`---(UNDO)->----------'
Use this command to modify a spline. To modify a spline, first identify the spline and then specify one of the following options:
POSITION:
The first point (pnt 1) indicates the old position, the second point (pnt 2) is the new position of the spline. This is the default.
TANGENT:
Use this option to change the tangent or slope at the specified point pnt 1. The tangent is determined by the direction vector of pnt 1 to pnt 2 or by a number (angle).
UNDO:
,------------------,
| |
v |
->(BSPL_POINT_LENGTH)-----|selection|--+--|segments|------+-----------+-(END)-->
| ^
| |
+--|pnt on spline|-+-|length|--+
^ |
| |
`-----------'
This command helps you to subdivide a bspline in pieces of same length. At first you have to identify the bspline and then to enter the number of segments. The command will create points at the beginning (resp. end) of each segment.
The second possibility is to pick a point on a spline and to enter a length. With a positive length, a point will be created on the spline right-hand from the picked point, with a negative length, a point will be created left-hand from the picked point.
->(BSPL_POLYGON_FEEDBACK)-----------+-> ON ---+------------------------------->
| ^
| |
+-> OFF --+
This function is used to determine your feedback type while creating bsplines (see BSPLINE). The default is BSPL_POLYGON_FEEDBACK OFF. This implies you have a full control of the shape during creation of bsplines. However, if you have a lot of points the feedback becomes slow because feedback for bsplines is time consuming. Switching BSPL_POLYGON_FEEDBACK to ON gives you a simple line typed feedback. The disadvantage is you have no longer control of the bspline shape.