|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> |
|
|
<html> |
|
|
<head> |
|
|
|
|
|
|
|
|
<meta name="Description" content="KLayout layout viewer and editor project page" /> |
|
|
<meta name="Keywords" content="KLayout OASIS GDS2 viewer editor layout semiconductor mask chip design" /> |
|
|
<meta name="abstract" content="KLayout is a free layout viewer and editor for several formats commonly used in the semiconductor industry to transfer layout data" /> |
|
|
<meta name="URL" content="https://www.klayout.de/" /> |
|
|
<meta name="Author" content="Matthias Koefferlein" /> |
|
|
<meta name="viewport" content="width=device-width, initial-scale=1"/> |
|
|
<meta http-equiv="Content-Script-Type" content="text/javascript" /> |
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
|
|
|
|
|
<title>KLayout Layout Viewer And Editor</title> |
|
|
|
|
|
|
|
|
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://www.klayout.de/news.xml"/> |
|
|
<link rel="stylesheet" type="text/css" href="https://www.klayout.de/format.css?v2.0"/> |
|
|
<link rel="shortcut icon" href="https://www.klayout.de/favicon.ico"/> |
|
|
|
|
|
|
|
|
<link rel="stylesheet" type="text/css" href="https://www.klayout.de/fonts.css"/> |
|
|
|
|
|
|
|
|
<script src="https://www.klayout.de/jquery-3.4.1.min.js"></script> |
|
|
|
|
|
|
|
|
<link href="https://www.klayout.de/bootstrap-4.3.1-dist/css/bootstrap.min.css" rel="stylesheet"> |
|
|
<script src="https://www.klayout.de/bootstrap-4.3.1-dist/js/bootstrap.min.js"></script> |
|
|
|
|
|
|
|
|
|
|
|
</head> |
|
|
|
|
|
<body> |
|
|
|
|
|
<div class="klayout-header"> |
|
|
|
|
|
<div class="container mb-5"> |
|
|
|
|
|
<nav class="navbar navbar-dark navbar-expand-lg"> |
|
|
|
|
|
<a class="navbar-brand" href="https://www.klayout.de"><img src="https://www.klayout.de/klayout.png" srcset="https://www.klayout.de/klayout-x2.png 2x" alt="KLayout"></a> |
|
|
|
|
|
<div class="collapse navbar-collapse" id="navbarToggleExternalContent"> |
|
|
|
|
|
<ul class="navbar-nav ml-auto mr-auto"> |
|
|
|
|
|
<li class="nav-item dropdown active mr-4"> |
|
|
<a class="nav-link dropdown-toggle klayout-menu" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> |
|
|
About |
|
|
</a> |
|
|
<div class="dropdown-menu" aria-labelledby="navbarDropdown"> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/intro.html">KLayout Project</a> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/doc.html">Documentation</a> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/galleries.html">Galleries</a> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/credits.html">Credits</a> |
|
|
<div class="dropdown-divider"></div> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/contact.html">Contact</a> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/impressum.html">Impressum / Imprint</a> |
|
|
<a class="dropdown-item" href="https://www.klayout.de/privacy_policy.html">Datenschutz / Privacy Policy</a> |
|
|
</div> |
|
|
</li> |
|
|
<li class="nav-item active mr-4"> |
|
|
<a class="nav-link klayout-menu" href="https://www.klayout.de/build.html">Get KLayout</a> |
|
|
</li> |
|
|
<li class="nav-item active mr-4"> |
|
|
<a class="nav-link klayout-menu" href="https://sami.klayout.org">Package Index</a> |
|
|
</li> |
|
|
<li class="nav-item active mr-5"> |
|
|
<a class="nav-link klayout-menu" href="https://www.klayout.de/forum">Forum</a> |
|
|
</li> |
|
|
<li class="nav-item active"> |
|
|
<span class="nav-link klayout-menu"> |
|
|
<a href="https://f-si.org"><img src="https://www.klayout.de/f-si_logo_32h_w.png" border="0" title="Free Silicon Foundation" alt="F-Si"/></a> |
|
|
<a class="ml-4" href="https://github.com/KLayout"><img src="https://www.klayout.de/GitHub-Mark-32px-white.png" border="0" title="KLayout on GitHub" alt="GitHub"/></a> |
|
|
</span> |
|
|
</li> |
|
|
|
|
|
</ul> |
|
|
|
|
|
</div> |
|
|
|
|
|
|
|
|
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarToggleExternalContent" aria-controls="navbarToggleExternalContent" aria-expanded="false" aria-label="Toggle navigation"> |
|
|
<span class="navbar-toggler-icon"></span> |
|
|
</button> |
|
|
|
|
|
</nav> |
|
|
|
|
|
</div> |
|
|
|
|
|
</div> |
|
|
|
|
|
<div class="container"> |
|
|
|
|
|
<h1>Known Bugs and Issues</h1> |
|
|
|
|
|
<p> |
|
|
Those are the known issues listed by the version in which they have been found. Unless noted, these |
|
|
bugs are fixed in the following release. |
|
|
</p> |
|
|
<p> |
|
|
<b>A note on bug tracking:</b> internally, I keep an issue |
|
|
tracker using the awesome Trac tool (<a href="http://trac.edgewall.org/">http://trac.edgewall.org/</a>). |
|
|
Currently that ticket database contains roughly 500 entries, ranging from refactoring ideas to critical |
|
|
bugs. The list below is an excerpt containing the issues with relevance for the end user |
|
|
community. |
|
|
</p> |
|
|
<p> |
|
|
If you encounter bugs not found in that list, please use to mail address listed on the contacts page or |
|
|
the forum to report issues. |
|
|
</p> |
|
|
|
|
|
<ul> |
|
|
<li><a href="#0.24.9">Version 0.24.9</a></li> |
|
|
<li><a href="#0.24.8">Version 0.24.8</a></li> |
|
|
<li><a href="#0.24.7">Version 0.24.7</a></li> |
|
|
<li><a href="#0.24.6">Version 0.24.6</a></li> |
|
|
<li><a href="#0.24.5">Version 0.24.5</a></li> |
|
|
<li><a href="#0.24.4">Version 0.24.4</a></li> |
|
|
<li><a href="#0.24.3">Version 0.24.3</a></li> |
|
|
<li><a href="#0.24.2">Version 0.24.2</a></li> |
|
|
<li><a href="#0.24.1">Version 0.24.1</a></li> |
|
|
<li><a href="#0.24">Version 0.24</a></li> |
|
|
<li><a href="#0.23.10">Version 0.23.10</a></li> |
|
|
<li><a href="#0.23.9">Version 0.23.9</a></li> |
|
|
<li><a href="#0.23.8">Version 0.23.8</a></li> |
|
|
<li><a href="#0.23.7">Version 0.23.7</a></li> |
|
|
<li><a href="#0.23.6">Version 0.23.6</a></li> |
|
|
<li><a href="#0.23.5">Version 0.23.5</a></li> |
|
|
<li><a href="#0.23.4">Version 0.23.4</a></li> |
|
|
<li><a href="#0.23.3">Version 0.23.3</a></li> |
|
|
<li><a href="#0.23.2">Version 0.23.2</a></li> |
|
|
<li><a href="#0.23.1">Version 0.23.1</a></li> |
|
|
<li><a href="#0.23">Version 0.23</a></li> |
|
|
<li><a href="#0.22.7">Version 0.22.7</a></li> |
|
|
<li><a href="#0.22.5">Version 0.22.5</a></li> |
|
|
<li><a href="#0.22.4">Version 0.22.4</a></li> |
|
|
<li><a href="#0.22.3">Version 0.22.3</a></li> |
|
|
<li><a href="#0.22.2">Version 0.22.2</a></li> |
|
|
<li><a href="#0.22.1">Version 0.22.1</a></li> |
|
|
<li><a href="#0.22">Version 0.22</a></li> |
|
|
<li><a href="#0.21.17">Version 0.21.17</a></li> |
|
|
<li><a href="#0.21.16">Version 0.21.16</a></li> |
|
|
<li><a href="#0.21.15">Version 0.21.15</a></li> |
|
|
<li><a href="#0.21.14">Version 0.21.14</a></li> |
|
|
<li><a href="#0.21.13">Version 0.21.13</a></li> |
|
|
<li><a href="#0.21.12">Version 0.21.12</a></li> |
|
|
<li><a href="#0.21.11">Version 0.21.11</a></li> |
|
|
<li><a href="#0.21.10">Version 0.21.10</a></li> |
|
|
<li><a href="#0.21.9">Version 0.21.9</a></li> |
|
|
<li><a href="#0.21.8">Version 0.21.8</a></li> |
|
|
<li><a href="#0.21.7">Version 0.21.7</a></li> |
|
|
<li><a href="#0.21.6">Version 0.21.6</a></li> |
|
|
<li><a href="#0.21.5">Version 0.21.5</a></li> |
|
|
<li><a href="#0.21.4">Version 0.21.4</a></li> |
|
|
<li><a href="#0.21.3">Version 0.21.3</a></li> |
|
|
<li><a href="#0.21.2">Version 0.21.2</a></li> |
|
|
<li><a href="#0.21.1">Version 0.21.1</a></li> |
|
|
<li><a href="#0.21">Version 0.21</a></li> |
|
|
<li><a href="#0.20.1">Version 0.20.1</a></li> |
|
|
<li><a href="#0.20">Version 0.20</a></li> |
|
|
<li><a href="#0.19.2">Version 0.19.2</a></li> |
|
|
<li><a href="#0.19.1">Version 0.19.1</a></li> |
|
|
<li><a href="#0.19">Version 0.19</a></li> |
|
|
<li><a href="#0.18">Version 0.18</a></li> |
|
|
<li><a href="#0.17.2">Version 0.17.2</a></li> |
|
|
<li><a href="#0.17.1">Version 0.17.1</a></li> |
|
|
<li><a href="#0.17">Version 0.17</a></li> |
|
|
<li><a href="#0.16.1">Version 0.16.1</a></li> |
|
|
<li><a href="#0.16">Version 0.16</a></li> |
|
|
<li><a href="#0.15">Version 0.15</a></li> |
|
|
<li><a href="#0.14">Version 0.14</a></li> |
|
|
<li><a href="#0.13">Version 0.13</a></li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.9"></a><h2>Version 0.24.9</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Inplace operators not working in Python with pya.Region</u> |
|
|
The application will crash when using the inplace operators ("+=", "-=" etc.) on |
|
|
the <tt>pya.Region</tt> object. |
|
|
A workaround is to use the explicit operator methods (like "__iadd__"): |
|
|
<pre> |
|
|
r1 = pya.Region() |
|
|
r2 = pya.Region() |
|
|
# will crash: |
|
|
r1 += r2 |
|
|
# will not crash: |
|
|
r1.__iadd__(r2)</pre> |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.8"></a><h2>Version 0.24.8</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Ruby integration is not compatible with Ruby 2.3</u> |
|
|
This prevents building on Ubuntu-16 which has deprecated Ruby 1.9 and only provides |
|
|
2.3 natively. Building your own Ruby 2.2 is a workaround. |
|
|
</li> |
|
|
<li><u>DEF reader issue</u> |
|
|
The DEF reader cannot digest combinations of MASK and via placements. |
|
|
</li> |
|
|
<li><u>DRC</u> |
|
|
Using RBA::Layout objects with DRC's "source" statement does not work. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.7"></a><h2>Version 0.24.7</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Problems on XOR in tiled mode with database units larger than 1 nm</u> |
|
|
The XOR tool does not work properly and may skip differences if the database |
|
|
unit is larger than 1nm and tiled mode is used. This bug will be fixed in 0.24.8. |
|
|
</li> |
|
|
<li><u>LEF reader does not read PINs with VIAs</u> |
|
|
PIN statements containing VIA objects will make the LEF reader abort with an |
|
|
error message. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.6"></a><h2>Version 0.24.6</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>A crash happens on "Edit/Make cells"</u> |
|
|
Sometimes a crash is observed if Edit/Make cells is used on a selection that contains |
|
|
instances of other cells.<br/> |
|
|
This bug will be fixed in 0.24.7. |
|
|
</li> |
|
|
<li><u>Problems on XOR with different database units</u> |
|
|
The XOR does not work as expected when different database units are present and tiling is enabled. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.5"></a><h2>Version 0.24.5</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>GC destroys plugin object returned by PluginFactory#create_plugin</u><p> |
|
|
The object returned from PluginFactory#create_plugin is not protected against |
|
|
destruction by the garbage collector which may lead to occasional crashes in the |
|
|
application. A workaround is to explicitly protect the object: |
|
|
<pre> def create_plugin(manager, main_window, view) |
|
|
pi = PluginTest.new |
|
|
pi._unmanage |
|
|
pi |
|
|
end |
|
|
</pre> |
|
|
This bug will be fixed in 0.24.6. |
|
|
</li> |
|
|
<li><u>Size function problems with slowly varying contours</u><p> |
|
|
For "almost parallel" connected edges, the sizing algorithm will produce |
|
|
incorrect output with spiky distortions.<br/> |
|
|
This bug will be fixed in 0.24.6. |
|
|
</li> |
|
|
<li><u>Diff tool issues when the input files contain different layers</u><p> |
|
|
The diff tool reports too many or too few differences if the input layouts contain |
|
|
different layers and one of the following options is used: |
|
|
<ul> |
|
|
<li>Summarize missing layers: OFF</li> |
|
|
<li>Run XOR on differences: ON</li> |
|
|
</ul> |
|
|
This bug will be fixed in 0.24.6. |
|
|
</li> |
|
|
<li><u>Search feature does not work on layers with names and layer/datatype specification</u><p> |
|
|
If layers with names and layer/datatype specification are present, the search feature does not |
|
|
work on shapes. The reason is a incorrect query which cannot be executed. A workaround is to |
|
|
edit the query in the "Custom" page: replace the layer expression (like "NAME (1/0)") by a plain |
|
|
layer/datatype specification. For example, replace |
|
|
<pre>shape on layer NAME (1/0) ...</pre> |
|
|
by |
|
|
<pre>shape on layer 1/0 ...</pre> |
|
|
and run the query from the custom page. |
|
|
<br> |
|
|
This bug will be fixed in 0.24.6. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.4"></a><h2>Version 0.24.4</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>OASIS writer: 1x1 array instances stop OASIS writer</u><p> |
|
|
The OASIS writer will refuse to write 1x1 array instances and bail out with an assertion. |
|
|
This bug will be fixed in 0.24.5. |
|
|
</li> |
|
|
<li><u>OASIS writer: wrong S_TOP_CELL property type when using standard properties</u><p> |
|
|
The property value is written as a "bstring", but it should be a "nstring". |
|
|
This bug will be fixed in 0.24.5. |
|
|
</li> |
|
|
<li><u>QFont, QColor and some other types cannot be assigned to QVariant</u><p> |
|
|
Unlike C++, QFont and QColor are not valid types storable within a QVariant. |
|
|
This currently leaves it impossible to change the font or colors for a QTreeWidgetItem for example. |
|
|
This bug will be fixed in 0.24.5. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.3"></a><h2>Version 0.24.3</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>OASIS writer: wrong S_TOP_CELL property when using standard properties with "Save Current Cell As"</u><p> |
|
|
Instead of writing the chosen top cell, the real top cell of the layout is written. |
|
|
This bug will be fixed in 0.24.4. |
|
|
</li> |
|
|
<li><u>OASIS reader: CELLNAME properties are not associated with cells</u> |
|
|
Instead CELLNAME properties are ignored. According to the specification, CELLNAME properties shall be |
|
|
associated with the cells described by the CELLNAME record. |
|
|
KLayout's OASIS writer will not produce such properties for cell-level user properties, so this is just |
|
|
an issue for externally created layouts. |
|
|
This bug will be fixed in 0.24.4. |
|
|
</li> |
|
|
</li> |
|
|
<li><u>OASIS writer: strict mode compatibility issues</u><p> |
|
|
Strict mode is not implemented with respect to these topics: |
|
|
<ul> |
|
|
<li>File level PROPERTY records are not put right at the beginning of the file</li> |
|
|
<li>Empty tables are not listed with 0 position</li> |
|
|
<li>Property value strings are not referenced by ID</li> |
|
|
<li>The property modal variables are referenced sometimes after name records (specifically CELLNAME with standard properties enabled). |
|
|
Instead, the name records reset these variables so this is not correct. Other reader may report errors for such files.</li> |
|
|
</ul> |
|
|
These bugs will be fixed in 0.24.4. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.2"></a><h2>Version 0.24.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Cells messed up in certain cases upon strict OASIS reading</u><p> |
|
|
Cells starting with a single "$" character and followed by a number (for example, "$1") |
|
|
may get messed up when reading strict mode OASIS. |
|
|
This bug will be fixed in 0.24.3. |
|
|
</li> |
|
|
<li><u>Single boxes will not vanish on undersize of a layer containing a single box</u><p> |
|
|
The DRC "size" operation does not size away small boxes (smaller than twice the sizing value) |
|
|
for layers containing a single box on top level only. |
|
|
This bug will be fixed in 0.24.3. |
|
|
</li> |
|
|
<li><u>Library references lost on load/reload</u><p> |
|
|
When using nested libraries (libraries referencing other libraries), cells may get lost |
|
|
when closing and reloading layouts. This bug will be fixed in 0.24.3. |
|
|
</li> |
|
|
<li><u>Crash on DRC files containing partial properties</u><p> |
|
|
DRC files with properties can be loaded into the marker browser, but will make the |
|
|
browser crash if the properties are not filled uniform - i.e. some markers are lacking |
|
|
some properties. This will be fixed in 0.24.3. |
|
|
</li> |
|
|
<li><u>Wrong type of RBA::SaveLayoutOptions#oasis_write_std_properties attribute</u><p> |
|
|
According to the documentation, the type of this attribute should be integer, since |
|
|
the accepted values are 0, 1 or 2. This will be fixed in 0.24.3. |
|
|
</li> |
|
|
<li><u>OASIS spec compliance issue in strict mode</u><p> |
|
|
Contrary to the OASIS specification, S_BOUNDING_BOX standard properties |
|
|
are not written into the cell table, but along with the cell itself. |
|
|
This will be fixed in 0.24.3. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.24.1"></a><h2>Version 0.24.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>"klayout_vo.exe" is not a pure viewer executable</u><p> |
|
|
The "klayout_vo.exe" binary found in the installation directory is not a pure "viewer-only" version |
|
|
as is was before. This will be fixed in 0.24.2. |
|
|
</li> |
|
|
|
|
|
<li><u>"Flip" and "Rotate" is not behaving properly sometimes</u><p> |
|
|
In a descended view, the "Flip" and "Rotate" functions do not maintain the center of the selection as |
|
|
they do in a non-descended view. Instead the shapes and instances are shifted far ways. This will be |
|
|
fixed in 0.24.2. |
|
|
</li> |
|
|
|
|
|
<li><u>Expressions using arithmetic operations between integers and floating-point values sometimes chose the wrong type</u><p> |
|
|
Expressions are used in search & replace operations for example. Among others, they provide arithmetic operations. |
|
|
When using binary arithmetic operators such as "+", the expression is evaluated with the first type. If that |
|
|
type is an integer, the computation is done in integers too. For example "to_i(2)+1.4" renders 3. |
|
|
The expected behavior (as seen in other languages) is to use floating-point arithmetics instead. |
|
|
This will be fixed in 0.24.2. |
|
|
</li> |
|
|
|
|
|
</ul> |
|
|
<a name="0.24"></a><h2>Version 0.24</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>PYTHONPATH environment variable needs to be set sometimes</u><p> |
|
|
In some cases, the PYTHONPATH environment variable needs to be set to point KLayout to the proper |
|
|
place for the Python libraries. This is the case if KLayout is built against a Python version that does |
|
|
not come with a proper PYTHONPATH built into it. This is not an issue when building against a |
|
|
Python package that comes with a Linux distribution or for the binary package on Windows.<br/> |
|
|
If the PYTHONPATH is required and not set correctly, the Python interpreter aborts on initialization. |
|
|
Unfortunately this a feature of Python and cannot be worked around easily. |
|
|
</li> |
|
|
|
|
|
<li><u>'Add all other layers' feature creates duplicate layers when named + unnamed layers are present</u><p> |
|
|
In several places, ".lyp" files can be combined with "add all other layers". This will create entries for |
|
|
layers not listed in the ".lyp" file. There is a bug in that feature if the ".lyp" file uses named layers and |
|
|
the layout does not and vice versa. For example, if the ".lyp" file specifies "NAME 1/0" for the layer source |
|
|
(name "NAME" and/or layer 1, datatype 0) and the layout is a GDS2 file which can only have a "1/0" layer, a |
|
|
new entry will be created with "NAME 1/0" because that layer is considered different from "1/0". <br/> |
|
|
This will be fixed in 0.24.1. |
|
|
</li> |
|
|
|
|
|
<li><u>Too aggressive optimization (RHEL 6) induces crashes in the net tracer</u><p> |
|
|
Apparently, the -O3 optimization used in the standard release build configuration is too |
|
|
aggressive for the gcc version present in RHEL 6 releases. Crashes have been reported in the |
|
|
net tracer module which appear to be related to that combination. A workaround is to reduce the |
|
|
optimization in the configuration file ("config/Makefile.conf.linux-64-gcc-release") to -O2.<br/> |
|
|
Because runtime effects appear to be minimal between -O3 and -O2 in recent CPU/compiler |
|
|
combinations, I'll switch to -O2 in version 0.24.1. |
|
|
</li> |
|
|
|
|
|
<li><u>Using shape method on ObjectInstPath object delivered by LayoutView#each_object_selected fails</u><p> |
|
|
In 0.24, the shape method became non-const to allow modification of the selection. But as an undesired side |
|
|
effect, "shape" cannot be called any more on the ObjectInstPath object delivered by LayoutView#each_object_selected. |
|
|
Hence the following code fails with a message saying that a non-const method (shape) cannot be called on a |
|
|
const object (s): |
|
|
|
|
|
<pre>view.each_object_selected { |s| puts s.shape.to_s }</pre> |
|
|
|
|
|
A workaround is to use a copy of the ObjectInstPath object: |
|
|
|
|
|
<pre>view.each_object_selected { |s| puts s.dup.shape.to_s }</pre> |
|
|
|
|
|
This issue will be fixed in version 0.24.1. |
|
|
</li> |
|
|
|
|
|
<li><u>StopIteration exception appears in the debugger (Python)</u><p> |
|
|
Python marks the end of an iteration sequence by raising a StopIteration exception. |
|
|
This exception appears in the debugger which is not desired. It should be ignored. This |
|
|
will be fixed in 0.24.1. |
|
|
</li> |
|
|
|
|
|
<li><u>Taking an iterator from a temporary object may crash the application (Python)</u><p> |
|
|
The following code causes an application crash since the object returned by "dup()" is short-living |
|
|
and the iterator delivered by "each()" does not keep a reference. Hence the object is destroyed before |
|
|
the iterator finishes: |
|
|
|
|
|
<pre> shapes = pya.Shapes() |
|
|
shapes.insert(pya.Box(0, 1, 2, 3)) |
|
|
for s in shapes.dup().each(): |
|
|
print(str(s)) |
|
|
</pre> |
|
|
|
|
|
A workaround is to assign the duplicate to a variable which lives longer: |
|
|
|
|
|
<pre> shapes = pya.Shapes() |
|
|
shapes.insert(pya.Box(0, 1, 2, 3)) |
|
|
shapes_dup = shapes.dup() |
|
|
for s in shapes_dup.each(): |
|
|
print(str(s)) |
|
|
</pre> |
|
|
</li> |
|
|
|
|
|
</ul> |
|
|
|
|
|
<a name="0.23.10"></a><h2>Version 0.23.10</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Problems reading CIF files with line breaks in P statements</u><p> |
|
|
Deviating from the spec, only single separator characters between x and y coordinate |
|
|
of points are allowed. This will be fixed in 0.23.11. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<ul> |
|
|
<li><u>DEF reader problems</u><p> |
|
|
The DEF reader takes 0 for the default path extension. The default extension |
|
|
should be half the width of the path. |
|
|
This will be fixed in 0.23.11. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<ul> |
|
|
<li><u>DRC crash on reading a layer that was overwritten</u><p> |
|
|
The following DRC script will crash, because in the "output" statement, the layer used for |
|
|
input a second time is overwritten: |
|
|
<pre> |
|
|
a = input(1) |
|
|
b = input(2) |
|
|
(b - a).output(1) |
|
|
# will crash, because a source has been overwritten by "output": |
|
|
(a - b).output(10) |
|
|
</pre> |
|
|
This will be fixed in 0.24. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.9"></a><h2>Version 0.23.9</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash when loading big images</u><p> |
|
|
When loading or creating big images (more than ~ 12k x 12k pixels) the application will |
|
|
crash. This is due to the limitation of Qt library which computes the memory requirement |
|
|
for an image as 32bit integer. |
|
|
<br/> |
|
|
Version 0.23.10 does not crash but rejects such images. In Ruby scripting, an option will be |
|
|
provided to create monochrom images. For rasterization purposes, this will extend the |
|
|
capabilities to creating images of more than 100k x 100k pixels. |
|
|
</li> |
|
|
<li><u>Crash when deleting a layer and something is selected on that layer</u><p> |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.10. |
|
|
</li> |
|
|
<li><u>Crash when deleting the top cell</u><p> |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.10. |
|
|
</li> |
|
|
<li><u>CIF reader compatibility</u><p> |
|
|
The CIF reader is not fully compatible with the CIF specification. For example, |
|
|
lower-case characters are not ignored as they should. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.10. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.8"></a><h2>Version 0.23.8</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DEF reader bug</u><p> |
|
|
E and W orientation on DEF PIN statements are swapped. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.9. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.7"></a><h2>Version 0.23.7</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DRC's inside and not_inside functions are not working</u><p> |
|
|
Sometimes shapes are reported as inside even though they are not. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.8. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.6"></a><h2>Version 0.23.6</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DRC crashes observed on repeated runs</u><p> |
|
|
This happens in particular if an input layer is overwritten. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.7. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<ul> |
|
|
<li><u>RBA::InputDialog::ask_double does not accept negative numbers</u><p> |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.7. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.5"></a><h2>Version 0.23.5</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DRC width/spacing check issue</u><p> |
|
|
In certain configurations (big polygons embracing smaller ones) width/spacing errors are reported more than once. The error count |
|
|
is too high. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.6. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.4"></a><h2>Version 0.23.4</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Ruby console issue</u><p> |
|
|
The following commands on the Ruby console make the program crash: "require 'net/http'; uri = URI('xyz')" |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.5. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.3"></a><h2>Version 0.23.3</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>UTF8 encoding ignored on XML files (will be fixed in 0.23.4)</u><p> |
|
|
UTF8 encoding is not implemented correctly for the XML reader. That is causing problems for |
|
|
macros containing characters with ordinals >= 128, for example german umlaut characters. |
|
|
This applies to all XML files, specifically .lym macros, where such characters are not read |
|
|
properly when they appear in the code or description texts for example. |
|
|
<br/> |
|
|
This issue will be fixed with 0.23.4. |
|
|
</li> |
|
|
<li><u>PCell context information in GDS files not backward compatible (will be fixed in 0.23.4)</u><p> |
|
|
GDS files with embedded PCell's written with previous versions (0.22.x and less) are not read correctly |
|
|
in some cases. Vice versa, PCell context information written with 0.23.x cannot be read by 0.22.x and less. |
|
|
</li> |
|
|
<li><u>Horizontal alignment broken for texts in default font (will be fixed in 0.23.4)</u><p> |
|
|
The scalable fonts work as expected. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.2"></a><h2>Version 0.23.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DRC: addressing layout views with the "@n" notation does not work</u><p> |
|
|
Addressing layout views using the "@n" notation in "target", "source" and |
|
|
"layout" gives an error about an undefined variable "i". |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23.1"></a><h2>Version 0.23.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Build issues with MacOS 10.9 (Xcode)</u><p> |
|
|
Currently, the source code does not build with Xcode on MacOS 10.9. Xcode uses the clang/LLVM compiler and |
|
|
unfortunately the issue could not be reproduced on Linux systems with clang 3.0 and 3.3. |
|
|
</li> |
|
|
<li><u>DRC issues related to database units</u><p> |
|
|
Multiple inputs with different database units do not work as expected and the database unit of output |
|
|
file generated by DRC scripts (target command) is always 0.001, regardless of the input file's database |
|
|
unit. |
|
|
</li> |
|
|
<li><u>DRC: log to file not working</u><p> |
|
|
The "log to file" function does not work as described. |
|
|
</li> |
|
|
<li><u>Wrong display context of markers produced by search and replace</u><p> |
|
|
Items in child cells are now shown relative to the current cell. Instead, the position in |
|
|
their direct parent cell is shown which typically does not match if the parent is not the |
|
|
current cell. |
|
|
</li> |
|
|
<li><u>Layer properties files not forward compatible</u><p> |
|
|
Since KLayout 0.23 introduced a new feature for .lyp files (valid/invalid layers), layer properties |
|
|
files written with version 0.23 and later cannot be read by older versions. This is because the |
|
|
XML reader was implemented in a strict fashion and will refuse to load files with unknown elements. |
|
|
This will be changed in the future, but it won't be ported back to the older versions. Hence |
|
|
the solution will not become effective immediately.<br></br> |
|
|
A workaround is to remove all "valid" elements from a .lyp file written by version 0.23. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.23"></a><h2>Version 0.23</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>RBA: Polygon#inside?, DPolygon#inside?, SimplePolygon#inside?, DSimplePolygon#inside? broken (Bugfix planned for 0.23.1)</u><p> |
|
|
The method reports false if only if the point is on the polygon edge. If the point is outside, the method |
|
|
reports true again. |
|
|
</li> |
|
|
<li><u>DRC: report database output is not working (Bugfix planned for 0.23.1)</u><p> |
|
|
Report database output is not working as described. Currently there is no simple workaround for that issue. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.7"></a><h2>Version 0.22.7</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>CIF reader broken (Bugfix planned for 0.22.8)</u><p> |
|
|
In many CIF files, GDS layer numbers are not assigned properly, resulting in |
|
|
duplicate or missing shapes. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.5"></a><h2>Version 0.22.5</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Net tracer issues (Bugfix planned for 0.23)</u><p> |
|
|
Performance may be poor in certain configurations, in particular when boolean operations |
|
|
are involved. In addition, the output generated by the net tracer's export function may contain |
|
|
many overlapping shapes. |
|
|
</li> |
|
|
<li><u>Net tracer does not work properly for OASIS file read on viewer mode (Bugfix planned for 0.23)</u><p> |
|
|
It is recommended to use editor mode when working with the net tracer. In viewer mode, |
|
|
OASIS shape arrays are used internally which slows down the net tracer and sometimes |
|
|
leads to wrong results. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.4"></a><h2>Version 0.22.4</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Macro IDE console issue</u><p> |
|
|
When the macro editor is closed and opened again the list of entries in the console |
|
|
is doubles. This may render huge configuration files. A quick workaround is to delete the |
|
|
line with the "<macro-editor-console-mru>" entry in the configuration file (on Linux |
|
|
in "$HOME/.klayout/klayoutrc") regularily. |
|
|
</li> |
|
|
<li><u>Crash when a view is closed while the "insert instance" form is open</u><p> |
|
|
KLayout crashes when a panel is closed while the "insert instance" form is still open. |
|
|
A workaround is to choose "Select" mode or hit Esc before closing a view. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.3"></a><h2>Version 0.22.3</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash when loading a layout while the net tracer is open</u><p> |
|
|
KLayout crashes when a layout is loaded into the current view while the net tracer |
|
|
is highlighting a net. |
|
|
</li> |
|
|
<li><u>Memory leak when stopping the XOR tool</u><p> |
|
|
When the XOR tool is stopped, some memory is not released. This will create |
|
|
a memory leak and that memory is no longer available for other features. |
|
|
</li> |
|
|
<li><u>Help index initialization can be cancelled</u><p> |
|
|
On the first start of a new version, the help system's index is generated. When this operation |
|
|
is cancelled, the help index may not be available fully. |
|
|
</li> |
|
|
<li><u>Instance placement: rotation and origin</u><p> |
|
|
when placing an instance at the bounding box (not the origin) and using a rotation angle, the |
|
|
reference point is not computed correctly and the instance is somewhat hard to place. |
|
|
</li> |
|
|
<li><u>The macro IDE occasionally crashes when trying to add a new location</u><p> |
|
|
When trying to add a new folder to the list of displayed macro locations, the application |
|
|
sometimes crashes with a segmentation fault. |
|
|
</li> |
|
|
<li><u>Some drawing issues</u><p> |
|
|
In some configurations (apparently related to cells rotated by arbitrary angles), |
|
|
the layout is not drawn correctly and artefacts may appear. |
|
|
As a workaround, this can be solved by disabling bitmap caching. |
|
|
</li> |
|
|
<li><u>Issues using multi-tab layer properties files as the default</u><p> |
|
|
Multi-tab layer properties files may not load properly (display more items per tab |
|
|
than desired) when used as default layer properties files. |
|
|
</li> |
|
|
<li><u>RVE file reading was broken in some cases (fixed by patch)</u><p> |
|
|
This happens when the number of comment lines is odd. |
|
|
The issue is fixed in 0.22.3-r1640 (see "Help/About" dialog). |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.2"></a><h2>Version 0.22.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Layer pollution happens when PCells or library cells are used</u><p> |
|
|
When multiple layouts are edited and PCells or library cells are instantiated, layers |
|
|
may be created in the current layout which belong to the other layout that is edited.</li> |
|
|
<li><u>Segmentation fault on drawing</u><p> |
|
|
When "bitmap caching" is enabled, a segmentation fault may happen during drawing in |
|
|
certain (rare) configurations.</li> |
|
|
<li><u>Shallow copy of instances is not working</u><p> |
|
|
Instead, "deep copy mode" is used always. In that mode, new cells are created when an |
|
|
instance is copy and pasted. The intended behavior is just to copy the instance, not the |
|
|
cell which is instantiated.</li> |
|
|
<li><u>Global configuration files override local ones</u><p> |
|
|
The previous (0.21.x) behavior was that local, per-user configuration files |
|
|
override settings from the global configuration file (in the installation directory). The |
|
|
intention was to provide a default configuration through global configurations. In 0.22.2, |
|
|
global configuration files always override per-user settings. That is not the intended |
|
|
behavior |
|
|
</li> |
|
|
<li><u>Arrow keys interfere with mouse movement</u><p> |
|
|
When the arrow keys are used while a selection is dragged with the mouse, the |
|
|
original shape is moved which results in a strange behavior. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.22.1"></a><h2>Version 0.22.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Copy & and paste of PCell or library instances across layouts does not work</u><p> |
|
|
Instead, the cell is duplicated, but it's no longer a PCell or library cell. |
|
|
</li> |
|
|
<li><u>"klayout -v" segmentation faults</u><p> |
|
|
The -v option is supposed to print the version number. After printing it, the executable terminates with a segmentation fault. |
|
|
</li> |
|
|
<li><u>Missing support for 'real' Unicode file names</u><p> |
|
|
Using Unicode filenames (i.e. Chinese) file names does not work properly. In particular these files are |
|
|
not opened on Windows. Unicode file names are not recorded properly in the "recently used" list. |
|
|
</li> |
|
|
<li><u>LEF import issues</u><p> |
|
|
The outline layer is not always generated correctly. Pin labels are not generated on pin shapes |
|
|
for LEF import. |
|
|
</li> |
|
|
<li><u>Crash on exit when the clipboard contains something</u><p> |
|
|
The application issues a segmentation fault on exit (or "is not working" on Windows) when the clipboard |
|
|
contains data. |
|
|
</li> |
|
|
<li><u>Ruby debugger crashes in some cases</u><p> |
|
|
In some cases (i.e. breakpoint in a widget callback) the debugger will crash with a "Stack level too deep" |
|
|
message. |
|
|
</li> |
|
|
<li><u>Instances of leaf cells are always copied "flat" to another layout</u><p> |
|
|
There is no way to copy the instance plus cells currently. |
|
|
</li> |
|
|
<li><u>Sometimes PCell variants remain as top level cells</u><p> |
|
|
If the Instance function is cancelled and a PCell was active, a new top cell will remain which |
|
|
holds the PCell that was about to be placed. These cells can be deleted manually, but that |
|
|
may be annoying. |
|
|
</li> |
|
|
<li><u>Help index cache may grow large</u><p> |
|
|
When switching between versions, the help index that KLayout creates once may grow larger every |
|
|
time a new program version is used. This can increase startup times of the program. |
|
|
</li> |
|
|
|
|
|
</ul> |
|
|
|
|
|
<a name="0.22"></a><h2>Version 0.22</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Edit/Select/Disable All not working</u><p> |
|
|
This function is supposed to disable all selectable items. Instead, an internal error message is issued. |
|
|
There is a patch for that problem <a href="http://klayout.de/forum/comments.php?DiscussionID=220&page=1#Item_3">here</a>. |
|
|
</li> |
|
|
<li><u>Build problems with gcc 4.0</u><p> |
|
|
There is a patch for that problem <a href="http://klayout.de/forum/comments.php?DiscussionID=216&page=1#Item_7">here</a>. |
|
|
</li> |
|
|
<li><u>GDS text size is based on micron instead of user units</u><p> |
|
|
Because of this the text object size may not be correct if the user unit is not micron. |
|
|
</li> |
|
|
<li><u>Arrow keys may behave differently</u><p> |
|
|
This can be annoying effects if you are used to a particular behavior. On the other hand, moving with the arrow |
|
|
keys now is possible in move mode. |
|
|
</li> |
|
|
<li><u>-z option works differently</u><p> |
|
|
"-z" not is a true "non-GUI" mode, in which no XServer connection is made on Linux. The advantage of this is that |
|
|
KLayout can be used as a engine on display-less servers. But some scripts depending on MainWindow or LayoutView objects |
|
|
will not work because these objects are no longer available. The solution will be to restore the original behavior |
|
|
of "-z" and implement a different, true display-less mode (i.e. "-zz"). |
|
|
</li> |
|
|
<li><u>Crash when using custom key bindings on some platforms</u><p> |
|
|
On some platforms, apparently Linux and recent Qt versions, KLayout crashes when custom key bindings are defined |
|
|
and the respective key is pressed. |
|
|
</li> |
|
|
<li><u>Issues with the macro tree</u><p> |
|
|
Drag & drop does not work correctly within the macro tree on Windows. KLayout crashes when trying to |
|
|
open a macro file that is not writable. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.17"></a><h2>Version 0.21.17</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Gerber file reader</u><p> |
|
|
SR command (step-and-repeat) is not supported currently. "AM" macro expansion does |
|
|
not work as expected: parameter expansion sometimes fails and the macro expansion does |
|
|
not use the units at definition but at instantiation. |
|
|
</li> |
|
|
<li><u>Copy & and paste of layers in layer tree</u><p> |
|
|
Layers are not copied to the current position but rather at the end of the layer tree. |
|
|
</li> |
|
|
<li><u>CIF writer does not correctly write OASIS circles</u><p> |
|
|
OASIS circles are represented as single-point paths with round ends. Such paths should |
|
|
be written as "R" round flash primitives to CIF. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.16"></a><h2>Version 0.21.16</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>"Save Current Cell As"</u><p> |
|
|
"Save Current Cell As" alters the state of the view. In effect, another "Save" or |
|
|
"Save Current Cell As" does not give the expected result. In particular, "Save" will |
|
|
repeat "Save Current Cell As" and not save the whole layout. |
|
|
</li> |
|
|
<li><u>Images take much memory</u><p> |
|
|
Images consume more memory than they are expected to. A single RGB pixel has a footprint |
|
|
of 15 Bytes. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.15"></a><h2>Version 0.21.15</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>No timestamps in GDS files</u><p> |
|
|
Currently, the time written into the GDS timestamp entries for BGNLIB and BGNSTR is a dummy value. |
|
|
</li> |
|
|
<li><u>DXF writer creates layer names with blanks</u><p> |
|
|
In some cases, in particular when writing layers with GDS layer/datatype plus a name, the DXF |
|
|
writer will create layer names with blanks in it. AutoCAD does not accept such files. |
|
|
</li> |
|
|
<li><u>Rendering of foreground objects</u><p> |
|
|
Foreground objects (i.e. rulers) are not rendered correctly in the printout. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.14"></a><h2>Version 0.21.14</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Initial cell not selected correctly in some cases</u><p> |
|
|
The largest cell is selected which may not necessarily a top cell. |
|
|
</li> |
|
|
<li><u>Excellon drill files not read</u><p> |
|
|
The PCB importer does not accept many Excellon drill files, in particular when they |
|
|
contain routes. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.13"></a><h2>Version 0.21.13</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Cells can be copied and pasted in viewer mode</u><p> |
|
|
That feature is not intended and does not work correctly. |
|
|
</li> |
|
|
<li><u>Resetting the configuration requires a restart of the application</u><p> |
|
|
Currently, Reset does not immediately reset the configuration. |
|
|
</li> |
|
|
<li><u>OASIS reader: overflow in g-deltas</u><p> |
|
|
Due to internal 32bit-processing, some g-deltas can be subject to overflow which gives |
|
|
wrong coordinates. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.12"></a><h2>Version 0.21.12</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Clip bug</u><p> |
|
|
The clip function does not work correctly if empty cells are present. |
|
|
</li> |
|
|
<li><u>CIF does not support command 93 (AREF)</u> |
|
|
</li> |
|
|
<li><u>Ruby scripts and Ruby 1.9</u><p> |
|
|
Some problems have been reported when using Ruby script and the Ruby 1.9 interpreter. This |
|
|
is in particular the case in the Windows executable. "Dir.glob" does not work correctly for example. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.11"></a><h2>Version 0.21.11</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>GDS2Text format not correctly recognized in some cases</u><p> |
|
|
The automatic detection of the GDS2Text format fails in some cases. |
|
|
</li> |
|
|
<li><u>Texts: strings with line breaks cannot be edited</u> |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.10"></a><h2>Version 0.21.10</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Command line option -p does not work correctly</u> |
|
|
</li> |
|
|
<li><u>OASIS writer problem</u><p> |
|
|
Layouts with large coordinates are not written to OASIS correctly in some cases. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.9"></a><h2>Version 0.21.9</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Moving a cell</u><p> |
|
|
The geometrical content of the instance is not drawn correctly in some cases. |
|
|
</li> |
|
|
<li><u>PCB import problems</u><p> |
|
|
When directly reading a PCB project (without using the assistant), some functions are |
|
|
broken (Bottom mounting mode, top cell, DBU). |
|
|
</li> |
|
|
<li><u>RVE file reader</u><p> |
|
|
The reader does not correctly handle check names with a dot. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.8"></a><h2>Version 0.21.8</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Layer properties files with tabs</u><p> |
|
|
The first tab's name is not read. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.7"></a><h2>Version 0.21.7</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Navigator</u><p> |
|
|
The navigator is broken. It is not functional if KLayout is closed with the navigator open. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.6"></a><h2>Version 0.21.6</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DXF reader</u><p> |
|
|
Arc interpolation of polylines does not work correctly. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.5"></a><h2>Version 0.21.5</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DXF reader</u><p> |
|
|
Bulges are not supported for polylines. |
|
|
</li> |
|
|
<li><u>Performance issues on select</u><p> |
|
|
Select (transient or on click) is slow in some cases. This happens in particular if cells in the |
|
|
hierarchy overlap heavily and many layers are present. |
|
|
</li> |
|
|
<li><u>RBA: Edge.intersect? delivers wrong results when the edges are collinear</u><p> |
|
|
The edges will be reported to intersect even if they don't. A workaround is to test if the bounding boxes |
|
|
overlap and the edges intersect. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.4"></a><h2>Version 0.21.4</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DXF reader</u><p> |
|
|
Some POLYLINE examples were using a global width which was overridden by a per-vertex width. In that case |
|
|
the global width is taken rather than the correct local one. |
|
|
</li> |
|
|
<li><u>Problems with non-english locales and UTF-8 file names on Linux</u><p> |
|
|
On KDE, files cannot be opened when the path contains non-ASCII characters on UTF-8 file systems. |
|
|
In some cases, the decimal point is inconsistently ',' instead of '.' which is the standard for KLayout. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.3"></a><h2>Version 0.21.3</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>CIF reader</u><p> |
|
|
The CIF reader currently does not understand "DS" commands without a scale specification (i.e. "DS 20"). It |
|
|
always requires two additional numbers specifying the scale as a ratio of two integers (i.e. "DS 20 1 10"). |
|
|
</li> |
|
|
<li><u>Rotate methods swapped</u><p> |
|
|
The clockwise rotate method rotates counterclockwise and vice versa. |
|
|
</li> |
|
|
<li><u>"Draw border instances of arrays" feature broken</u><p> |
|
|
Much is drawn and much more isn't ... |
|
|
</li> |
|
|
<li><u>Ruby crash</u><p> |
|
|
On some systems, the program crashes when a ruby script is loaded (i.e. with the "-rm" option) with |
|
|
a message "[BUG] terminated node (0x2a9708ca70)" or similar. This seems in particular to |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.2"></a><h2>Version 0.21.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>DXF reader still not complete</u><p> |
|
|
In particular, interpretation of POLYLINE and LWPOLYLINE entities is not clear yet. In comparison to |
|
|
other converters, no merging of separate lines into polygons is provided. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21.1"></a><h2>Version 0.21.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>RBA: RdbItem.each_value is not working on const objects</u><p> |
|
|
This is important, because const RdbItem objects are commonly encountered when scanning through a marker |
|
|
database with RBA. |
|
|
</li> |
|
|
<li><u>DXF reader still not complete</u><p> |
|
|
The interpretation of certain features (i.e. array instances, extrusion direction) is not clear yet. |
|
|
</li> |
|
|
<li><u>Layer mapping broken for DXF and CIF readers, writers</u><p> |
|
|
Incorrect layers are written for example when a layer subset is written. In addition, mapping or selection of |
|
|
input layers does not work correctly for DXF and CIF readers. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.21"></a><h2>Version 0.21</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Persistency of reader options is broken</u><p> |
|
|
The program does not remember reader options when the dialog is closed. |
|
|
</li> |
|
|
<li><u>RBA: each_selected is broken</u><p> |
|
|
A segmentation fault occurs on Windows in the "each_selected" method of LayoutView. |
|
|
</li> |
|
|
<li><u>DXF and CIF readers and writers incomplete</u><p> |
|
|
DXF and CIF readers and writers implement only very basic features. Some important capabilities are |
|
|
missing, in particular for the DXF part. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.20.1"></a><h2>Version 0.20.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Program crashes when the marker browser is opened</u><p> |
|
|
When the marker browser is opened with a maximum number of markers set to a value not equal to 1000 (the default), |
|
|
the program crashes if the marker browser window is opened from the menu (it works when the marker database is loaded |
|
|
from the command line with the -m switch). |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.20"></a><h2>Version 0.20</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Net tracing does not extract net correctly</u><p> |
|
|
This bug is related to branching conditions. In such cases, a net might not be extracted correctly. |
|
|
</li> |
|
|
<li><u>Gerber reader does not correctly read certain macros</u><p> |
|
|
The "outline" macro is read as a thin outline also in the "closed" case by the RS274X reader. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.19.3"></a><h2>Version 0.19.3</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Polygon cut algorithm for reducing the number of points per polygon in the GDS2 writer</u><p> |
|
|
When the GDS2 writer has to reduce the number of points of a polygon, it will cut the polygon into smaller pieces. |
|
|
Under some circumstances, this algorithm fails. To avoid this problem, use the Multi XY record mode if possible. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.19.2"></a><h2>Version 0.19.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crashes on Qt 4.6.0</u><p> |
|
|
Due to a bug in Qt's QPixmap constructor in Qt 4.6.0, KLayout does not work with this version. |
|
|
</li> |
|
|
<li><u>Ruby modules not loaded from the installation path on UNIX</u><p> |
|
|
In most cases, ruby modules are not looked for in the wrong path. The intention was to search for ".rbm" files in the |
|
|
directory where KLayout is installed. Instead, the current or any other directory is searched depending on how the |
|
|
KLayout executable is specified on the command line. |
|
|
</li> |
|
|
<li><u>OASIS reader too picky</u><p> |
|
|
The OASIS reader does not accept files with forward references of the special "S_GDS_PROPNAME" property name.<p> |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.19.1"></a><h2>Version 0.19.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>"Test for shapes in view" feature does not work properly for AREF's</u><p> |
|
|
In some cases, array references are not considered and layers appear to be empty even if they are not. |
|
|
</li> |
|
|
<li><u>RBA scripts crash in tight loops on Ruby 1.8.7 (i.e. Ubuntu 9.10)</u><p> |
|
|
That is a ruby problem (http://www.ruby-forum.com/topic/198545). The problem is known and a new libruby version should be available soon. |
|
|
</li> |
|
|
<li><u>GDS text reader problems</u><p> |
|
|
In some build environments, problems have been encountered with GDS text files with negative values. |
|
|
</li> |
|
|
<li><u>Interactive stretching of images is broken</u><p> |
|
|
The interactive stretching of images with the square handles is sometimes leading to invalid results and does not |
|
|
work properly. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.19"></a><h2>Version 0.19</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash when selecting "..." node in the marker browser item list</u><p> |
|
|
The item list is abbreviated using a dummy item labelled "...". When clicking at this item, the application crashes. |
|
|
</li> |
|
|
<li><u>"Test for shapes in view" feature in layer list is extremely slow in some cases</u><p> |
|
|
This feature marks a layer "unused" when now shape is shown on that layer in the view area. Currently, the application |
|
|
becomes very slow in some cases when this option is used. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.18"></a><h2>Version 0.18</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash when selecting "instance" mode on empty layout</u><p> |
|
|
When the layout is empty (no cell present, i.e. top cell was deleted) and "Instance" mode is selected in editor mode, |
|
|
the program crashes with an internal error. |
|
|
</li> |
|
|
<li><u>Issues on Mac OS X</u><p> |
|
|
There are still some issues on Mac OS X, as well for the build as for the program itself - in particular |
|
|
with Qt 4.5.x. For example, with accessibility enabled, the program crashes when a file is loaded. This will be fixed |
|
|
in version 0.18.1. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.17.2"></a><h2>Version 0.17.2</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Sizing bugs</u><p> |
|
|
The sizing function sometimes produces invalid results, in particular when doing a strong undersize. |
|
|
</li> |
|
|
<li><u>Build not working for Mac OS X</u><p> |
|
|
The 'ar' call has been changed such that the Mac OS X build should work now (not tested since no |
|
|
test system was available). |
|
|
</li> |
|
|
<li><u>Crash when double-clicking a path end in partial mode</u><p> |
|
|
When double-clicking on a path end in partial edit mode (dragging just the path end), the program crashed in some cases. |
|
|
</li> |
|
|
<li><u>'Fit selection' is not working properly</u><p> |
|
|
Not all instances are taken into account. |
|
|
</li> |
|
|
<li><u>Wrong DBU read from GDS2 files</u><p> |
|
|
The DBU per user unit is used, which is not correct. Instead the DBU per meter unit should be used. |
|
|
</li> |
|
|
<li><u>Round paths are not written properly to OASIS files</u><p> |
|
|
</li> |
|
|
<li><u>Windows repaint problem for hidden canvas content</u><p> |
|
|
Strange effects occure when a non-modal front dialog is moved over the canvas area. |
|
|
</li> |
|
|
<li><u>Space representation in vector fonts</u><p> |
|
|
Space characters are not represented. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.17.1"></a><h2>Version 0.17.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Program hangs if the properties dialog is closed with the system menu</u><p> |
|
|
When the properties dialog is closed using the system menu (the "X" button in the window title bar), KLayout |
|
|
goes into an unusable state. This does not happen if the dialog is closed using the "Close" button. |
|
|
</li> |
|
|
<li><u>Program crashes if many text objects have identical location</u><p> |
|
|
This happens if more than 100 text objects are present that have identical locations. |
|
|
</li> |
|
|
<li><u>OASIS reader problems when property name and string ID's are defined after they are used</u><p> |
|
|
This was a known limitation but came up recently in a certain application. |
|
|
</li> |
|
|
<li><u>AREF row and column description was swapped and misleading</u><p> |
|
|
In GDS files, row and column vectors can be arbitrary x/y value pairs. However, some tools implement |
|
|
a more strict interpretation in which only orthogonal row and column vectors are allowed. Also, |
|
|
row and column must be oriented in a certain way. In addition, the description of row and column vectors is |
|
|
swapped. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.17"></a><h2>Version 0.17</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Display freezes on some Windows installations</u><p> |
|
|
Apparently due to a problem with Qt's grabMouse function on some Windows installations the display freezes when |
|
|
a zoom box or selection box is opened. By switching to the Task manager using "Ctrl+Alt+Del", the display can be unfrozen |
|
|
but zoom or selection operations a not possible. This problem existed in all previous versions as well and apparently |
|
|
occured in particular on Windows XP. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.16.1"></a><h2>Version 0.16.1</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Some flaws in partial edit mode and polygon or path creation</u><p> |
|
|
In certain cases, the closing point of polygons was not created correctly, path segments did not snap correctly to 45 degree edges or |
|
|
partial edit mode was behaving in a strange way. |
|
|
</li> |
|
|
<li><u>Order of recent file list was latest last</u><p> |
|
|
... which is contrary to what other programs implement. |
|
|
</li> |
|
|
<li><u>Selection of very large arrays happened to be very slow</u><p> |
|
|
This happened because many markers have been drawn for such arrays. This has been changed such that the array is not drawn as individual markers |
|
|
for large arrays. Instead, a representative geometrical description is given. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.16"></a><h2>Version 0.16</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Compile problems when ruby support is not enabled</u><p> |
|
|
KLayout won't link unless ruby support is enabled (-rblib, -rbinc on build.sh given). |
|
|
</li> |
|
|
<li><u>"open recent" function is not working correctly on Windows</u><p> |
|
|
The file names are not stored properly in the config file - thus "open recent" does not |
|
|
work since backslashes are dropped. |
|
|
</li> |
|
|
<li><u>"change layer" function is not working properly</u><p> |
|
|
Sometimes an error is issued saying that the requested layer already exist (but it does not). |
|
|
Undo support is not implemented correctly. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.15"></a><h2>Version 0.15</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Child cells are shown multiple times in cell hierarchy</u><p> |
|
|
Under certain circumstances, child cells are shown multiple times in the cell tree, i.e. |
|
|
a cell "A" which is a child of "TOP" might appear multiple times in the tree below "TOP". |
|
|
This is not intended - child cells are supposed to appear just once, even if instantiated |
|
|
multiple times. |
|
|
</li> |
|
|
<li><u>"Save" saves all layers if none should be saved</u><p> |
|
|
If the layers to be saved are confined, i.e. to visibles ones, it may happen that, if |
|
|
no layer is visible for example, all layers are saved instead. A workaround is to create |
|
|
a new layer (i.e. layer 1000, datatype 0) and save it. Such an empty layer will be saved but |
|
|
won't appear in the OASIS or GDS2 file, since it does not contain any shapes. |
|
|
</li> |
|
|
<li><u>Text objects are not shown correctly if a scalable font is selected for them</u><p> |
|
|
Depending on the transformation of the text, the text may appear at unexpected locations for |
|
|
example. A workaround is to use the "default" font. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.14"></a><h2>Version 0.14</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash on Windows the first time when the program is called:</u><p> |
|
|
On windows, crashes have been observed, when the program is started the first time after |
|
|
installation. This indicates some problem with Qt installation in the registry. |
|
|
However, this bug was not tracked down yet, because it is not easy to reproduce. |
|
|
Since it only happens once, it is not considered pretty serious. |
|
|
</li> |
|
|
</ul> |
|
|
|
|
|
<a name="0.13"></a><h2>Version 0.13</h2> |
|
|
|
|
|
<ul> |
|
|
<li><u>Crash on Windows when the layer list becomes very small:</u><p> |
|
|
The program crashes on Windows, if the layer list becomes too small to be displayed. |
|
|
This happens for example, if at the default size of the program window, the color panel, the frame color panel |
|
|
and the stipple panel are opened in that order. Then, the height of the layer list becomes a few pixels |
|
|
and the program crashes. |
|
|
</li> |
|
|
<li><u>KLayout does not start on some platforms and exits with a segmentation fault:</u><p> |
|
|
This problem has been found on the 64bit Ubuntu 7.10 platform for example. The program does not start up |
|
|
and exits immediately with a segmentation fault.<p> |
|
|
Here is a small patch that fixes that problem:<p> |
|
|
<pre> |
|
|
layApplication.h:53 |
|
|
Application (int &argc, char *argv []); |
|
|
instead of: |
|
|
Application (int argc, char *argv []); |
|
|
|
|
|
layApplication.cc:50 |
|
|
Application::Application (int &argc, char *argv []) |
|
|
instead of: |
|
|
Application::Application (int argc, char *argv []) |
|
|
</pre> |
|
|
</li> |
|
|
|
|
|
</ul> |
|
|
|
|
|
|
|
|
</div> |
|
|
</body> |
|
|
</html> |
|
|
|
|
|
|
