HD88536: PART : EDGE FILLET : CATIA FREEZE (LOOP) WHILE UPDATING EDGE FI LLET AND CANCEL BUTTON DOES NOT WORK.

APAR status

• Closed as suggestion for future release.

Error description

• SCENARIO:
  1. Start CATIA V5
  2. Open the CATPart
  Workbench-
  Part Design
  3. Double click the EdgeFillet.1 to edit it.
  The
  Edge Fillet Definition panel appears.
  4. Change radius to 1mm
  5. Click on the OK button.
  The Update in progress panel
  appears.
  6. Click on the Cancel button.
  It is canceled.
  7.
  Click on the Update All icon.
  The Updating panel appears.
  8.
  Click on the Cancel button.
  PROBLEM:
  CATIA goes into loop
  (Freeze) The cancel button does not work.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS APAR IS CONSIDERED AS A SUGGESTION FOR IMPROVEMENT FOR
  CATIA.
  PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN ORDER TO OPEN
  A REQUIREMENT FORM.
  Additional Closure Information:
  INCIDENT
  DIAGNOSIS: CATIA loop while updating and CANCEL button does
  not work.
  DEVELOPMENT REQUEST JUSTIFICATION:
  While
  editing some specific features like fillet, an interrupt
  mechanism is put in place while building the geometry. It is
  because feature edition command instantiates its own progress
  bar and geometry building regularly asks the command to
  refresh the progress bar. The refresh of the progress bar also
  ensures that CANCEL button is active and that interruption can
  be asked to geometry building algorithm.
  Why CANCEL does not
  work during update?
  Features are only called on a model and it
  cannot create a progress bar. Update command computes list of
  features that needs to be updated. Then puts a callback on
  their update event, and asks for part feature update. Update
  command then refreshes the progress bar each time it is called
  on the callback, during the update event. This means that
  during an individual feature build, the update command is not
  called and the progress task is not refreshed.
  Pushing the
  CANCEL button has the following effect:
  The interruption is
  caught by the operator when the update command refreshes the
  progress task. This calls a callback which raises an update
  exception, which is caught at the place where the part update
  is asked and finishes the update by closing the progress task.
  Therefore it is complicated to put in place a mechanism that
  would allow a given feature to itself provide an interruptible
  task during the global update. This is will require a new
  mechanism during update command.
  This is a new specification
  and development altogether which can only be done through an
  enhancement request.
  

APAR Information

• 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