IBM Support

HD24358: DEFINESTANDALONESECTION METHOD DOESN'T WORK WITH A PRODUCT DOCU MENT WHICH AGGREGATE A V4 MODEL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • DefineStandAloneSection method doesn't work with
    a product document which aggregate a V4 model.
    .
    I have to create "Section-Cuts" in the Drafting-
    Workbench without "Front-Views".
    .
    The program is in C++, but for creating
    the "Section-Cuts", I use the VB-functions
    .
    CATIAGenerativeViewBehavior-
    >DefineStandAloneSection(in CATSafeArrayVariant
    profil,
    in CATBSTR type_of_section,
    in CATBSTR type_of_profile,
    in CATSafeArrayVariant iPlane,
    in short iSide)
    .
    with
    .
    CATIAGenerativeViewBehavior->put_Document(in
    CATIABase iDocument).
    .
    .
    But this program doesn't work with product
    document which aggregate a V4 model.
    .
    I've provided our application which use this method
    inside the DassaultHotline.zip sip file.
    .
    To use it, you have to :
    - Open Product1.CATProduct file from
    ProductWithV5CATPart zip file
    - Create a drafting
    - Launch the CENASC command
    from "Automatische Schnittansichten" toolbar
    - Click inside the Part/Produkt editor
    - Select the product.1 product
    - Click inside the Scnittebenen editor -> a small
    panel will appear
    - Select the plane zx
    - Click OK on the small panel and on the big one ->
    a section-cut appear.
    .
    If you repeat again this senario with the
    ProductWithV4Model zip file , the section cut will not
    created.
    .
    You can see the result with the
    Drawing1.CATDrawing files.
    .
    

Local fix

Problem summary

  • DefineStandAloneSection method doesn't work with
    a product document which aggregate a V4 model.
    .
    I have to create "Section-Cuts" in the Drafting-
    Workbench without "Front-Views".
    .
    The program is in C++, but for creating
    the "Section-Cuts", I use the VB-functions
    .
    CATIAGenerativeViewBehavior-
    >DefineStandAloneSection(in CATSafeArrayVariant
    profil,
    in CATBSTR type_of_section,
    in CATBSTR type_of_profile,
    in CATSafeArrayVariant iPlane,
    in short iSide)
    .
    with
    .
    CATIAGenerativeViewBehavior->put_Document(in
    CATIABase iDocument).
    .
    .
    But this program doesn't work with product
    document which aggregate a V4 model.
    

Problem conclusion

  • THIS PROBLEM IS PERMANENT RESTRICTION IN Digital
    Manufacturing and Prod.
    Additional Closure Information:
    THIS PROBLEM IS PERMANENT RESTRICTION IN
    CATIA.
    .
    Incident Diagnosis
    API CAA DefineStandAloneSection does not work
    correctly when generating section view from
    Product on which V4 model has been inserted.
    .
    .
    Restriction Explanation
    The section view is defined by a plane and a profile
    (profil argument). Customer creates profil by an
    infinite line (limit model). The problem is model
    limits are different between V4 and V5. 100000 in
    V4 and 1000000 in V5. Section View is not created
    from V4 model because input data are out of range.
    .
    .
    By-Pass
    You don't need to create infinite line. If you create
    a limited line, it works.
    For example, you can retrieve the boundary box of
    the 3D model from the feature by using
    CATI3DGeoVisu services:
    - Retrieve a pointer pMyRep to CATI3DGeoVisu
    from the feature.
    - Get the rep by using GiveRep
    CAT3DRep* p3DRep = (CAT3DRep*) pMyrep-
    >GiveRep();
    CAT3DBoundingSphere 3DSphere = p3DRep -
    >GetBoundingElement();
    float boundRadius = 3DSphere.GetRadius();
    by using boundRadius you can create limited line.
    .
    

Temporary fix

Comments

APAR Information

  • APAR number

    HD24358

  • Reported component name

    CATIA V5/NT/200

  • Reported component ID

    569151000

  • Reported release

    511

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2004-06-28

  • Closed date

    2011-11-04

  • Last modified date

    2011-11-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"511","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 November 2011