Stats

  • Locked Locked
  • Replies 0
  • Subscribers 143
  • Views 7706
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

When ddGetObj is used for a constraint file, it appears to do more than just getting the object

Byron Caloz

This is what I put in a script:

; sv is the schematic cell view

cobj = ddGetObj(sv~>libName sv~>cellName "constraint" nil nil "r")

I need the object to get various data within the constraint file.

My intent is NOT to change the file or the constraints in any way.

Yet when this happens it appears as if the constraint manager wakes up and finds problems with the constraints and puts the constraint cache in edit mode.

I don't want this to happen, so I added the following code:

if(cobj then
  cc = muffleWarnings(ciCacheGet(sv))
  if( cc then
    muffleWarnings(ciCacheDiscardEdits(cc))
    muffleWarnings(ciCacheMakeReadOnly(cc))
  )
)

I am concerned that there would be problems for users when actually attempting to make changes in the constraint or might undo changes they had made previously.

what is the best way to access constraint data without waking up the constraint manager?

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.