1. Bugfix: avoid an internal error because in set_db highlight()
was called before setup_trees(). Error was:
Internal error: ../../../src/laybasic/laybasic/layNetlistBrowserPage.cc:387 model != 0 was not true in LayoutView::show_l2ndb
2. Provide GSI binding for lay::NetlistBrowserDialog
* First implementation.
* PORT BACK: fixed a few flaws (fixed-width side panel ..)
1. On "save as" the filename displayed in the cell view selection box
was not updated
2. The width of the library and cellview panel could not be reduced
below the width of the combo boxes in the headers. So the
panels might have become pretty wide without being able to reduce
them.
* Implemented #560 (multiple techs on libraries)
* WIP: added basic feature and tests.
* WIP: provide tests are GSI binding of new antenna check
* Fixed issue #579 (perimeter_only mode for antenna check)
* Updated DRC doc for 'perimeter_only'
Iterated instances are created for OASIS files
using irregular repetitions in viewer mode.
Reason: this way, the same drawing optimization
than for iterated shape arrays can be applied.
As this is a new API feature, some adjustments
had to be made to incorporate them into the
code.
* Maybe fixed a performance issue on box-trees: the iterator wasn't
going down to the very bottom of the tree on initialization
* Added array quad skipping in display of shape arrays
While doing this, it was discovered that the problem also
persists for EdgePairs and Texts.
In order to provide a more generic solution, some refactoring
was applied.
* First implementation of the perimeter factor for antenna check, unit tests.
* Bugfix and unit tests for GSI binding of new antenna check version.
* DRC integration of perimeter-enabled antenna check.
* Enhanced DRC doc for antenna rule
The solution is to provide a new layer type: text collections.
This layer type can be manipulated by
* Boolean AND and NOT with polygons
* Polygon interact with texts
* Flatten
* Text filters
Layers of this kind are generated through "labels" now in LVS
and DRC. Text layers are more consistent than the previous
solution which consisted of pseudo-labels embedded inside
polygon layers.
Side effect: with text layers the dummy boxes for the text
markers (2x2 DBU boxes) are gone.
Text layers can participate in LVS connect and connect_global.
Text layers are the preferred way to handle texts in DRC and LVS.