Stats

  • Locked Locked
  • Replies 12
  • Subscribers 143
  • Views 19597
  • 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

Help on getting Library names for all instances on display form

venuuuuu

 Hi guys,

 I tried some code to  get  Library names for all instances on display form. I get it  But Display form doesnot work properly .

 Error is shown below

 *Error* TrShapeReportToPort: too few arguments (2 expected, 1 given) - (db:246261804)

 

 

 cv = geGetEditCellView()
procedure( TrShapeReportToPort( cv outport )
cv = geGetWindowCellView( cv )
;cv = geGetEditCellView()
librarys=nil
fprintf(
outport
"%s %s %s contains library's:"
cv~>libName cv~>cellName cv~>viewName
)
foreach(libryname cv~>instances~>libName
foreach(singlelib librarys
if(singlelib!=libryname then
librarys=cons(libryname librarys)
)
)
)
foreach(libname librarys
fprintf( outport "\n%-10s %-10s" "Library" libname )
)
list( cv~>libName cv~>cellName cv~>viewName )
)

TrReportBBox = '((120 729) (372 876))
procedure( TrShapeReport( cv )
thePort = outfile( "/tmp/ShapeReport.txt" )
when( thePort
TrShapeReportToPort( cv thePort )
close( thePort )
) ; when
view( "/tmp/ShapeReport.txt" TrReportBBox "Librarys" )
) ; procedure
hiSetBindKey("Layout" "Ctrl<Key>1"      "TrShapeReportToPort(cv)")

  • Why not use the code I posted previously (in the post before your last one) which does exactly that? 

    Your code is hard to read (indentation makes code much easier to understand), and is always going to have support for finite levels of hierarchy if it's written this way (I'm not talking about the lack of indentation, but the whole approach). Using recursion (as I used in my code) will mean that it can keep traversing the hierarchy no matter how many levels of hierarchy you have.

    Regards,

    Andrew.

  •  Thank you Andrew. It works good and meets my requirements. Thank you very much. And sorry, to made mistake in code(post before your previous post)

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.