|
When migrating AUXVIEW2 views from V4 to V5, there are several things
you need to do to ensure that your migration results will be equivalent to
your AUXVIEW2 defaults.
What you need to do depends on whether you want to use generative view
styles or settings (defined via Tools > Options).
- Customize V5 generative view styles XML files: these make it possible
to customize the appearance and behavior of a V5 generative view via a
set of pre-defined parameters and options, and customize V4 to V5 DRAW
settings via Tools > Options > Compatibility.
OR
- Customize V5 Drafting settings via Tools > Options >
Mechanical Design > Drafting.
Generative view styles offer more customization possibilities than
settings. |
 |
This section explains the methodology for managing AUXVIEW2 defaults
for V4 to V5 migration. |
 |
About AUXVIEW2 Defaults Management for V4 to V5
Migration
When managing AUXVIEW2 defaults for V4 to V5 migration, you will need to
bear the following information in mind:
- It is a CATIA administrator who manages V5 generative view styles
definition.
- In V5, generative view styles are defined via the Standards Editor:
Tools > Standards, generativeparameters category.
- A complete standard definition is stored in a XML file. For example,
DefaultGenerativeStyle.xml defines the default Drafting generative view
styles.
- In V5, a .CATDrawing uses only one generative view style: when a new
.CATDrawing is created, only one generative view style defined in the
Standards Editor (and stored in a single XML file) can be referenced and
is embedded in the .CATDrawing.
- Whatever the defaults of the AUXVIEW2 view were prior to being copied
into CATIA Version 5, once in V5, they are those defined either in the
selected generative view style or in the settings (Tools > Options
> Mechanical Design > Drafting).
For more information, refer to the Administration Tasks chapter and to
the Customizing chapter in the Generative Drafting User's Guide.
Referencing the Project File (PRJ)
Before starting the migration process, you need to reference in V5 the
project file (PRJ) used to create the V4 2D model. To do this, go to
Tools > Options > General > Compatibility > V4 Data Reading
tab, and fill in the PROJECT File Path and DLNAME fields.
|
|
|
 |
The PRJ files must be renamed on UNIX before being installed on a
Windows system: all the "±" (plus or minus sign) must be replaced by "_"
(underscore) in PRJ filenames. For example, my±filename.prj on Unix must be
renamed my_filename.prj |
|
Preparing for AUXVIEW2 Migration with Generative
View Styles
The procedure below describes what you need to do before migrating
AUXVIEW2 views from V4 to V5 if you use generative view styles:
-
Start a V5 session.
Note: Step 2 must be performed with a session running in
administrator mode, but the following steps can be performed with a
session running in normal mode.
-
Customize the V5 generative view styles XML file that you
want to use when migrating AUXVIEW2 views from V4 to V5. For more
information on customizing generative view styles, refer to the
Administration Tasks chapter in the Generative Drafting User's
Guide.
-
Go to Tools > Options > Mechanical Design >
Drafting > Administration tab and make sure that the Prevent
generative view style creation setting is not selected.
-
Go to Tools > Options > General > Compatibility
> V4/V5 DRAW tab, and, from the Default generative view style
list, select the XML file that you just customized to specify that this
generative view style should be used when migrating AUXVIEW2 views from
V4 to V5.
|
| |
Preparing for AUXVIEW2 Migration with Settings
The procedure below describes what you need to do before migrating
AUXVIEW2 views from V4 to V5 if you use settings:
-
Start a V5 session (you do not necessarily need to be
running the session in administrator mode).
-
Go to Tools > Options > Mechanical Design >
Drafting and on the various tabs, define the settings that you want
to be applied when migrating AUXVIEW2 views from V4 to V5.
|

|
In the Knowledge Base
For detailed information regarding the parameters that you need to modify
in the generative view styles XML files, refer
About Managing AUXVIEW2
defaults migration from V4 to higher versions. |
|
 |