Stats

  • Locked Locked
  • Replies 12
  • Subscribers 128
  • Views 17470
  • 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

Showing contents of a cell while dragging

Grover

In Layout (I'm using 6.1.3.500.13) , there are these bindkeys Shift-F and Ctrl-F to show/hide the contents of instances in the layout. Now when I drag an instance around, the contents of the instance disappear. In "hide contents mode" (Ctrl-F) an outline of the cell is shown, but in "show contents mode" (Shift-F) the entire cell disappears and you're basically moving an invisible ghost with flight lines. Needless to say this is cumbersome when you want to move instances with any degree of accuracy.

This doesn't happen with polygons on the current level of hierarchy; these always remain visible while dragging. Is there a way to make this happen with instances as well?

  •  Is there a status update on this topic?  I see the exact same problem, but I have not tried it in 6.1.4.  When dragging (adding, copying) an instance from another library nothing is seen, not even the bounding box.  More specifically, if the  library where the instance is placed is not using the same binary techfile as the library the instance is coming from, nothing is seen.  If the the library in which the instance is being placed is attached to the techfile in the library from which the instance is coming from, the issue is not seen.  Also, recompiling the technology file in the source library on the same machine by the same user solves the issue.  There seems to be something about an incompatibility between the two binary techfiles compiled under different environments.

  • I would suggest you contact Cadence Customer Support (http://support.cadence.com ) about this. If the technology files are not compatible (e.g. they use different layer numbers between the two), then it's quite possible you won't see anything, because the data will end up on the same layer numbers as it did to start off with. If they have the same layer/purpose definitions (particularly the layer numbers and purpose numbers match) then there should not be a problem, even if they are separately compiled binary tech databases.

    Best Regards,

    Andrew.

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.