* Copy & and paste of PCell or library instances across layouts did not work
Instead, the cell was duplicated, but it's no longer a PCell or library cell.
* "klayout -v" was segmentation faults
The -v option is supposed to print the version number. After printing it,
the executable terminates with a segmentation fault.
* 'Real' unicode file names could not be used
Using Unicode filenames (i.e. Chinese) file names did not work properly.
In particular these files were not opened on Windows. Unicode file names were
not recorded properly in the "recently used" list.
In version 0.22.2, unicode files names can be used in all places on Windows
and Linux.
* Some LEF import issues solved
The outline layer was not always generated correctly. Pin labels were not generated
on pin shapes for LEF import.
* KLayout was crashing on exit when the clipboard contained something
The application issued a segmentation fault on exit (or "is not working" on Windows)
when the clipboard contained data.
* Ruby debugger crashed in some cases
In some cases (i.e. breakpoint in a widget callback) the debugger crashed with a
"Stack level too deep" message.
* Instances of leaf cells were always copied "flat" to another layout
There was no way to copy the instance plus cells before this was fixed.
* Sometimes PCell variants remain as top level cells
If the Instance function was cancelled and a PCell was active, a new top cell remained
which held the PCell that was about to be placed. These cells could be deleted manually,
but that may be annoying.
* Help index cache was growing large in some cases
When switching between versions, the help index that KLayout creates once grew larger
every time a new program version was used. This increased startup times of the program.
* An "abs" function was missing expressions
* Experimental support for 64bit coordinates is provided.
To enable 64bit coordinates, use "-with-64bit-coord" on the build script. This feature
requires gcc >= 4.4 and a 64bit platform. 64bit coordinate support is "experimental"
because of some known issues (i.e. it is possible to write corrupt GDS files with such large
coordinates). OASIS on the other hand supports 64bit coordinates.