pdaOPSdual

A base class for multi-layer operations with target layer.

You can use the elements doc and tex to document the operation. This is often useful for later changes as the logic behind complex chains of operations is often not easy to follow by colleques and/or partners.
Attributes:

Structure

The attributes and elements are shown below, in a sorted per type fashion.
In case a list is printed after an element, it indicates that you can have many, otherwise it should be a single element. With a optional it tells the element is not required.

<layerAnotB  
A="..."  B="..." ... > ...
  <doc> ... </doc>    optional
  <groupRef> ... </groupRef>   list
  <markup> ... </markup>   list
  <tex> ... </tex>   list
  <ticket> ... </ticket>   list
</layerAnotB>

XSD

The schema file can be downloaded or viewed at xPDK_Layout.

Details

A

Type pdaGDSlayerReference documentation:

B

Type pdaGDSlayerReference documentation:

doc

Type pdaDocumentation documentation:
This field allows some (short, single line) documentation to be written. It can be a long string, but the idea is not to replace a design manual.
This field is like tex which allows documentation in LaTex format; doc is restricted to plain text.

groupRef

Type groupRef documentation:

markup

Type pdaMarkupDocumentation documentation: actual html.

tex

Type pdaTexDocumentation documentation: doc , but tex can be a long text in LaTex format to document the layer in more detail if needed.

You can document anything relevant for the topic you want to define.

Multiple paragraphs is fine. Format is Latex, so more complex content is possible.

ticket

Type pdaTicket documentation: