HD11858: REGENERATION OF DELETED OR HIDDEN ENTITIES WHEN A 2D DRAWING I S UPDATED

APAR status

• Closed as suggestion for future release.

Error description

• 1. Open the CATDrawing
  2. Delete or put in no-show the generative shape
  or the outline of the clipping view
  3. c:force update
  RESULT:
  Features reappear
  
  .
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS APAR IS CONSIDERED AS A SUGGESTION FOR IMPROVEMENT WHICH C
  ANNOT BE INCORPORATED IN VERSION 5 RELEASE 13
  PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN ORDER TO OPEN A REQUI
  REMENT FORM.
  Incident Diagnosis
  The generative drafting application manages a
  persistency of some graphical dress-up during the
  update process. That means that after an element
  has been generated during view update, the user
  may dress it up with:
  - Show/Noshow
  - color
  - linetype
  - thickness
  - Delete
  ...Then during the next update of the view, the
  drafting application will re-apply this dress-up to
  the new generated element. This behaviour is
  linked to the fact that the generated element knows
  which 3D element it corresponds to (face, edge,
  application element, etc...)
  Not all drafting elements have the information
  required to support this persistency. This is why
  some lemeents will keep their dress-up suring
  update, and some tothers will not.
  For example generated shapes do not support this
  mechanism, so they will re-appear during update
  after having been put in noshow.
  The list of elements whose dress-up persistency is:
  - Geometry corresponding to a physical edge or
  face of a 3D element
  - Axis-lines
  - Center-lines
  - Threads
  Elements whose graphic dress-up persistency is not
  supported is the following:
  - Generated shapes (hatching in sections and
  breakout views)
  - edges corresponding to symbolic visualization of
  fillets
  - edges representing limits of clipping, detail or
  broken views
  - Annotations generated from 3D annotations or 3D
  applcation elements (structure, piping)
  Development Request Justification
  Upgrading some elements so that they support this
  persistency mechanism is an enhancement request
  (which implies changing the data structure)
  This development request has currently no
  targeted release.
  Answer and By-Pass
  None
  
  .
  

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