|
) w* y4 P v/ t不行,我早就试了。你要先了解这两个属性。A part instance is a part you have placed on a schematic page. A part occurrence is created each time the part instance occurs in a schematic that is within the design hierarchy. So, for example, placing a part on a schematic page in your design creates both an instance and an occurrence. You can assign properties to the part instance, in which case the property (and its associated value) will "shine through" to each part occurrence unless the value is specifically replaced by a value on an individual part occurrence. The Property editor window graphically illustrates the state of instance and occurrence properties.
2 c3 k5 v$ w2 Y. w; U8 T1 nThe instance property values shines through to the occurrence as long as the occurrence property values have not been edited in any way. When you explicitly edit an occurrence property value or when Capture modifies it via one of its tools, the occurrence values overrides the instance value. Only the occurrence value will be placed in the netlist. If you...
# E8 Z: }; M+ Y | The result will be...# ?: c; }( M, y9 B& T" s
| place a part on an unused page in your design
$ E4 [8 }. [1 X, U | only instance properties on that part.( @ I' T+ l% b
| place one part in the root schematic. f% c# G. q |' p3 L
| one set of instance properties and one set of occurrence properties on that part.
_4 _6 f9 U) ~$ F }/ C% I( ? | do not modify the occurrence properties on an object/ @4 u, r4 L: w! u5 z) m2 |" v
| instance properties will "shine through" on the occurrence. The instance properties themselves may be shining through from the library definition (or design cache if the two differ& M2 l9 E/ q- q
| edit a part in a library5 F# E3 p- Z$ V3 P! E
| no effect on the part in any project.
8 Y. x+ q( {2 v/ M4 X6 ^+ R3 ~2 J5 W& o |
* k, ?) H% r* T" U- K) }* _+ b: R
% E: w6 h# r$ `. O |
|