IBM Support

HD47376: PROBLEM WHEN USING BUILDREP METHOD OF MACHININGAREA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • Problem when using BuildRep method of
    MachiningArea.
    .
    SCENARIO:
    - Build our sample workspace ᄄWksVisuMachFeatᄄ
    on V5R15.
    - Launch CNEXT.exe. Open our sample
    document, ᄄSample_MachiningArea.CATProcessᄄ.
    - Switch to Prismatic Machining workbench.
    - Launch ᄄCreate Machinable Featureᄄ command,
    and select a face.
    -->Then, the MachiningArea
    (CAAMachinableFeature.4) is created, and Dialog is
    displayed.
    --> BuildRep() is called for all existing
    MachiningArea.
    (5) Press the Cancel button.
    -->The created MachiningArea is deleted.
    Confirm that BuildRep() is called for all existing
    MachiningArea (CAAMachinableFeature.1~3)
    on the console window. (Set
    CNEXTOUTPUT=console)
    .
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • This incident is closed as USER error.
    .
    Incident Diagnosis:
    An undo notification is sent when the Cancel button
    is pressed. This is linked to the use of the
    GetCancelState() method.
    .
    In this case, the father of the previously created
    features (the Manufacturing View object or
    MfgView) is warned that it has been modidifed.
    As this notification is general, at the level of the
    Manufacturing View it is not possible to know what
    is happening. We don't know if a feature has been
    added to the MfgView, or removed or just modified.
    .
    So we need to completely update the MfgView visu
    and all the 3D reps of all the children need to be
    updated.
    .
    There is no direct correction of this problem, but a
    workaround can be implemented to avoid this
    global visu update.
    .
    Correct Application:
    The target is to avoid the global visu update, so I
    propose not to use anymore the GetCancelState().
    To replace it, the command that creates the
    features needs to delete them in case of cancel.
    .
    A sample code has been attached to this IR as
    material. It shows how to manage the deletion of a
    created feature and how the update the feature
    tree.
    .
    The code is an example on the
    CAAMachinableFeature, the same thing need to be
    coded for any other created feature
    (CAAMachinableGeom).
    .
    Documentation Reference:
    See closure description.
    .
    

APAR Information

  • APAR number

    HD47376

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    515

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-12-06

  • Closed date

    2005-12-23

  • Last modified date

    2005-12-23

  • 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"515","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
23 December 2005