Stats

Replies 4
Subscribers 158
Views 13159
Members are here 0

axlSelectByProperty

I have 4 components with the property PART_NUMBER= AD8362ARU in my design. To select them all at once, there is a skill function, axlSelectByProperty. it works for nets for example: p = axlSelectByProperty("net" LOGICAL_PATH") returns 472 DBIDs. Then, why axlSelectByProperty("compdef" "PART_NUMBER" "AD8362ARU") returns only one DBID not all 4? axlSelectByProperty("compdef" "PART_NUMBER") returns 112 item, axlSelectByProperty("compdef" "PART_NUMBER" "*AD8362ARU*" t) returns only one! Is it a bug? or a bad use...?

Subsidiary question, why carriage return(newline) are not correctly ddisplayed in messages I post in this forum?

Originally posted in cdnusers.org by willbi

archive over 18 years ago

to get the only empty line we see, I have to write
twice in the message...

Originally posted in cdnusers.org by willbi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
archive over 18 years ago
I read the message about formatting code...

Then newlines must be there....

willbi

Originally posted in cdnusers.org by willbi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
archive over 18 years ago

There is only one "compdef" record (one component definition record) called AD8362ARU. There may be four, or four hundred, "compinst" records (instances of the component) but only one component definition record.

Originally posted in cdnusers.org by AshCan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
archive over 18 years ago

OK, so it's normal that I have only one DBID... with compdef.

In fact, I copy/paste the last try and then it was compdef.... but with component it should work.

axlSelectByProperty("component" "PART_NUMBER" "AD8362ARU") returns "nil"!

What's wrong?

there is 4 components with the property PART_NUMBER=AD8362ARU....

I found that with compdef (which returns only one), car(p)->components length is 4!

So I have my list... thanks.

Originally posted in cdnusers.org by willbi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Cadence Guidelines

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.