Matthias
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
About
- Username
- Matthias
- Joined
- Visits
- 1,521
- Last Active
- Roles
- Member
Comments
-
Hi Ray, I found the bug in the "save visible only" feature. It also applied to CIF writing. Thanks for reporting that issue. I'll put the fix in the next minor release (0.21.2). I have not installed TrueView yet to track down the reading…
-
Hi, Sorry for not mentioning that here. Yes it is. I changed to code above so it is a full Ruby module. Copy the code into some file, i.e. "multiclip.rbm" and run KLayout (version 0.21.1) like this: klayout -rm multiclip.rbm ... If you …
-
Hallo, basically you can use KLayout non-interactively. If you run KLayout this way: klayout -e -z -r script.rb ... you can run the script without bringing up a GUI. You can pass arguments to the script by defining Ruby variables, i.e. klayout …
-
Hi Kalle, you're welcome :-) Actually you have not been the only one mentioning that issue. Since MinGW is well supported as a build platform at least on 32bit it was not a big deal to create the package. I'll maintain this build for the next vers…
-
Hi Kalle, I provided a new binary package made with MinGW which is very similar to the ones I provided before. Lacking a W2K installation, I cannot check the package myself but I am very confident that this solves that issue. The package is availa…
-
Hi Kalle, For the Windows build, I had to switch from MinGW to Visual Studio 2010 as the build system for clean 64 bit support. Unfortunately Microsoft has dropped support for Windows 2000 on VS2010. It is still possible to build KLayout on MinGW.…
-
Hi chhung, I forgot to mention that new feature in the release notes. Actually, I replaced the simple substitution scheme by a full-blown expression parser. The new scheme is described here: http://klayout.de/short_um.html#ruler_properties. Frankl…
-
Hallo, thanks for reporting that issue. I'll provide a bug fix in 0.21.1. Best regards, Matthias
-
Hi Jean-Yves, The current version 0.21 already has a "detailed" check box in the net tracer dialog to show the cell instance details. It's also worth mentioning the text export which allows to produce a text file containing the net items…
-
Hi chhung, Even though Nokia does not state that explicitly, the setTabPosition method seems to require Qt 4.5 at least. For 4.4 it is sufficient to comment out that line. I'll add a #if to allow building with earlier versions of Qt in the next re…
-
Hi sedborg, I can reproduce the problem. It seems to be related to the build which is based on Ruby 1.9 and MSVC instead of 1.8 and MinGW. I'll try to trace down the problem and provide a fix in the next version 0.21.1. Best regards, Matthias
-
Hi Ray, It looks like I was dropping too much from the DXF files - namely the layer flags. From the documentation I understood that almost everything is optional in DXF, but obviously that is not the case. I have enhanced the writer and right now …
-
Hi Jean-Yves, by "instances" I assume you mean the placement and orientation of the specific cell, right? Internally, the transformation of the cell in the top cell is known. I can extend the display so it not only shows the cells but th…
-
Hi Acku, With the next release (0.21) it will be possible to write a ruby script that creates the desired clips and saves them to individual GDS files using the integrated ruby interpreter (RBA). This will be far easier than modifying the C++ code…
-
Hi, I would suggest to create a ruby script that does that - however, right now, the clip function is not provided as a ruby method and it's pretty tedious to emulate it. I'll consider that as a suggestion for the next release (which hopefully will…
-
Hi Nicolas, I guess I think what happened: by coincidence, two instances of KLayout were writing the same config file thus the content got mixed up. This I can avoid by some kind of locking. Since I was spending some effort to keep the configuratio…
-
Hallo, Thank you for that problem report. The configuration file is located in you home directory and is called ".layviewrc". If you rename this file, KLayout should start with a blank configuration. If it is possible, you can send the …
-
Hi Jean-Yves, I assume you are trying to do something like that: v = ... # get RBA::LayoutViewl = v.begin_layerswhile !l.at_end? l.current.visible = true l.nextend This will fail because "l.current" is basically just a pointer to an i…
-
Hi scholi, I assume the problem is caused by the DATATYPE specification. For TEXT objects, there is no DATATYPE, just TEXTTYPE. I'd suggest to try this: def addText(self, pos, txt, height=None, mag=22.22222, layer=0, width=0, dose=1,angle=0):# hei…
-
Hi, thank you for that feedback. It's very encouraging ... :-) Thanks for reporting the internal error. I think it's worth looking at. I'll try to figure out what caused that logic error. Best regards, Matthias
-
Hallo, frankly, the XOR is coded in some straightforward but not quite efficient way. Basically, it collects all the shapes (in fact: their edges) from the layout and runs a scanline boolean over it. Even in medium-size cases this implies a conside…
-
Hi Jim, in order to run an XOR, you need to load both layouts into the same panel. The XOR will be done between the two top cells you have selected. By default "Layout A" will be the first, "Layout B" the second file you have lo…
-
Thank you for taking care of that. Matthias
-
Hi all, Kaspersky has removed klayout.exe from their signature files. Lately, all versions have been reported to contain a virus. Kaspesky has confirmed that it was a false positive and changed their signatures accordingly. klayout.exe now is clean…
-
Hi Salvatore, I admit the description is somewhat misleading. "select visible layers only" will select all layers for saving that are switched to visible in the layer panel. In the current version 0.20.2 that feature seems to be working …
-
Hi Oliver, you are right, mouse events can't be handled with ruby scripting yet, but it's a good suggestion. So far I have focused on drawing of primitives rather than "physical structures". For that, KLayout is lacking the infrastructur…
-
Hi Oliver, there is a short documentation here: http://klayout.de/advanced_um.html#net_tracing. Basically, it's intended as a visualization tool, not a layout extraction feature. It follows a net from a given point and highlights all connected sh…
-
Hi Chhung, Right now, the browser uses the selection style for highlighting. You can edit the selection style on the "Application/Selection" page in the setup dialog. There you can specify a particular color, line width and other settings…
-
Hi chhung, There is the cell instance browser which you could use. Goto "Tools"->"Browse Instances". In the dialog that appears press "Choose Cell". In the cell selection dialog choose the cell whose instances you …
-
Hi Iftikhar, The bad alloc error is probably indicating that the process exceeds the 2 GB process size limit (I guess you are using a 32 bit executable). That large memory allocation is likely a consequence of the flattening of the fill cells. You…