Hi Jim,
you can use master or any other branch, but without warranty.
The usual approach (and the one favoured by GitHub) is: features are developed in branches. When they are considered stable enough they are integrated into the master (pull request). Hence the master is kind of "latest greatest", but with a certain risk of being spoiled. There are also forks from other user with their own masters and branches. Don't confuse them with the ones from the KLayout project.
But eventually, when the master is considered to have a sufficient quality, a release is made by creating a release tag (https://github.com/KLayout/klayout/releases). A release is a snapshot which is then turned into Windows binaries, Linux packages, PyPI wheels etc. This this is a lengthy process and I don't want to do this too often.
Matthias
Hi Sergey,
currently, the highlights are shown in the same style as the selection. You can choose the style on the "Display" page in the setup dialog ("How the selection is shown").
In the next release it will be possible to ch…
Hi Salvatore,
currently there is no such functionality available. Unfortunately there is little support for deleting cells in Ruby scripts, so there is no simple way to add this functionality with a Ruby script.
However, it's a very good suggestio…
Hi roman,
In contrast to GDS2, OASIS specifies paths by half the width. This value must be a multiple of the database unit. An path with a width that is an odd multiple of the database unit therefore must be rounded so that it can be written to an …
Hi,
I would like to mention that the "installation directory" lookup mechanism does not work properly in some circumstances (in particular on Linux). The "-c" option is very likely the most robust way to specify a certain file. …
Hi Kenji,
KLayout reads layers by layer and datatype (indicated by the "layer/datatype" notation in the layer list).
Maybe I don't understand the remark correctly. Could you be more specific?
Best regards,
Matthias
Hi Kenji,
usually the memory requirements are somewhat lower than the (uncompressed) GDS file size (i.e. 1.4G load into 700M of memory). However, when the layout contains many properties attached to shapes or instances or a huge number of cells, th…
Hi,
the segmentation fault was probably a bug: when a text was selected in a child cell, the script did not work properly. I changed the code above accordingly.
Currently there is not a good method to provide user interfaces with ruby scripts. The…
Hi,
applying one change to multiple objects in the selection is not straightforward unfortunately for internal reasons. That is something to go into some "search & replace" functionality.
For your use case however as usual there is a…
Hi,
The following script may be helpful to fulfil your request: It dumps the absolute coordinates of all text objects selected to a file in the format "TEXT(x,y)".
Here is the code:
class MenuAction < RBA::Action def initialize( tit…
Hi,
In order to make the text objects show up in the given orientation and size you need to select a vector font and check the "Apply text scaling and orientation" check box on the "Display" page in the "Setup" dialog.…
Hi,
Unlike Calibre's DRC files there is no equivalent LVS error database which is supported by open source tools (at least not one I know). That's why there is no support for LVS error browsing right now.
In principle it would be possible to open …
Hi,
thanks for the hint about the speed issue. I'll try to reproduce that and find a solution for it.
Regarding the second request: there is a check box in the property page named "absolute (accumulated) transformations". Thats probably …
Ok, I assume that's the bounding box of the cell then.
If that is correct, this is a simple extension for the script: just replace line 41 by a calculation of the box area and the division by the latter:
active_cv = lv.cellview(lv.active_cellview_…
Hi Roman,
KLayout can read Calibre DRC database files.
To load a DRC database, open the marker browser ("Tools"->"Marker Browser") and press the "Open" button.
Best regards,
Matthias
Looks like I have to check the code again.
Until then, it should be possible to avoid that problem by disabling the reading of properties using the "Reader Options" dialog in the "File" menu.
Best regards,
Matthias
Hi Scott,
it looks like your editor pasted the RTF content, not just the code text.
I provided a download link for the code here. This one should work.
Best regards,
Matthias
Hi Joaquim,
I received that request already a couple of times.
However, I am lacking a good example currently. Do you have a link to a public source of LEF/DEF sample files?
Best regards,
Matthias
Hi Joaquim,
in the lastest version 0.19.3 you can set an environment variable $KLAYOUT_PATH which points to the directory containing the .rbm files.
Best regards,
Matthias
Hi roman,
I guess KLayout is somewhat too picky about the structure.
The basic problem is that OASIS allows forward references which are hard to resolve in a single-pass parser. Single-pass parsers have the advantage of operating Faster on gzipped…
Hi Joaquim,
KLayout derives the installation path form the $0 argument. I learned that shells behave differently and for some shells the absolute path cannot be derived from that argument.
Currently, one workaround is to start KLayout with the ful…
Hi,
there is actually a nice function which pretty much does what you need.
Select the instance and choose "Descend" from the Display menu or hit Ctrl+D. You can return to the previous level by choosing "Ascend" or Ctrl+A.
KLa…
Hi,
currently, that functionality is not provided as a standard feature.
It is possible however, to implement such a function in ruby. Just copy the code below to a file with extension .rbm (i.e. compute_area.rbm) and copy that file into the insta…
Hi Jay,
I still can't reproduce it, but there was some fishy code in the reader which I suspect was the reason for the problems.
It should be fixed in 0.19.2.
Best regards,
Matthias
Hi Jay,
I suspect there is an interaction with LOCALE settings. I am not aware that the reader uses the current locale but I wouldn't rule out that possibility.
What are your language settings (i.e. output of "locale")?
Best regards,
M…
Hi Jay,
that is really strange. The reason why I am asking for Qt is that the keyboard shortcuts are interpreted by Qt. Maybe the Qt version on Fedora 7 does not like these shortcuts and produces invalid results when the shortcut strings are retrie…