Index: trunk/doc/user/06_features/hierarchic/index.html =================================================================== --- trunk/doc/user/06_features/hierarchic/index.html (revision 10195) +++ trunk/doc/user/06_features/hierarchic/index.html (revision 10196) @@ -134,10 +134,28 @@
So all in all, the intermediate method uses two different addressing -methods: the ./ name prefix to keep something sheet-local and -no-prefix prefix names, which are called automatic and simply end -up being global in the intermediate use case. +methods: the ./ name prefix to keep something sheet-local; and +names with no prefix, which are called automatic, which simply end +up being global. (At least in the intermediate use case). +
+In case of the classic "CPU board" example, the intention is that all the U1 +symbols are merged together into a single big CPU component. In case of the +LED example, the same Q1 on different child sheet instances should be different +FETs. This problem is the very same problem as with the networks, and the +soluiton is the same: name prefixing. In fact, components have the same +name prefixes and the same behavior as nets. +
+In the actual examples, this was achieved: +
+This rule of network and symbol name prefixes work the same is true for +the more advanced use cases, for the rest of this document as well, although +the document will use networks to demonstrate different tricks.
@@ -165,7 +183,7 @@
This is the same mechanism that the GND symbol uses. -
The intermediate setup covers the situation of reusable single-sheet modules, locking internal networks and components into the sheet local scope @@ -297,10 +315,11 @@ if the object is not found, it is created in the project global namespace. -
+Not yet supported. (TODO) - -
Not yet supported. (TODO)