S
Suresh Jeevanandam
Guest
Hi,
I used ROD rectangles extensively in my layout as contacts, the
advantage being the number of rows and columns are automatically changed
when the metal shape changes. Now later found that I should use a
different size. Is there any SKILL function to access the sub parts of a
ROD rectangle and modify their properties.
I do not know why the properties form does not show any information
about the sub parts. However, for the ROD path the sub parts are fully
accessible from the GUI, though there is no procedural way to do that.
I doubt if these ROD rectangles are intended to be used in layouts at all,
-- there is no way to create them interactively, ( Through procedural
way one can create the first rectangle, and copy and use it
interactively then onwards).
-- Once created there is no way you modify the sub parts, not even read
the properties.
If that is the case there can at least be a note in the docs saying to
not use them in layout.
I do not know why these software designs are so poor, not even thought
of how the user is going to use it for the very basic operations. [
Another thing I simply hate is the CDF mechanism]
ROD objects :
-- do not have any PI way of reading or modifying there sub parts
-- not compatible with dbMoveFig, dbCopyFig
-- can cause crashes if you do edit-in-place
regards,
Suresh
I used ROD rectangles extensively in my layout as contacts, the
advantage being the number of rows and columns are automatically changed
when the metal shape changes. Now later found that I should use a
different size. Is there any SKILL function to access the sub parts of a
ROD rectangle and modify their properties.
I do not know why the properties form does not show any information
about the sub parts. However, for the ROD path the sub parts are fully
accessible from the GUI, though there is no procedural way to do that.
I doubt if these ROD rectangles are intended to be used in layouts at all,
-- there is no way to create them interactively, ( Through procedural
way one can create the first rectangle, and copy and use it
interactively then onwards).
-- Once created there is no way you modify the sub parts, not even read
the properties.
If that is the case there can at least be a note in the docs saying to
not use them in layout.
I do not know why these software designs are so poor, not even thought
of how the user is going to use it for the very basic operations. [
Another thing I simply hate is the CDF mechanism]
ROD objects :
-- do not have any PI way of reading or modifying there sub parts
-- not compatible with dbMoveFig, dbCopyFig
-- can cause crashes if you do edit-in-place
regards,
Suresh