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,515
- Last Active
- Roles
- Member
Comments
-
Hi Canny, I'm sorry, but I can't reproduce that behaviour myself. Did you build Qt yourself? AFAIK RHEL does not come with Qt 4.6.2. Maybe some issue with your Qt build? Are you able to reproduce the issue with the Windows binary? Regards, Matth…
-
Hi, KLAYOUT_PATH is just used to identify libraries, load scripts and locate Ruby/Python modules. It does not change the behaviour of RBA::Layout#read. Like with every well-mannered method there is no hidden functionality within RBA::Layout#read. …
-
Hi Dave, you mean within a script? Here is one: ly = RBA::CellView::active.layout# layer/datatype of the mask layersmask_layers = [ [ 1, 0 ], [ 2, 0 ]]bbox = RBA::DBox::newmask_layers.each do |l,d| li = ly.find_layer(l, d) if li iter = ly.…
-
Hi Theo, Looks like a there is a performance trap here. I think I can provide a solution in 0.24.4. Best regards, Matthias
-
Hi Canny, that looks like a recursive call within Qt. I have never seen that message before. Maybe an issue with the Qt installation? What's your platform and Qt version? Matthias
-
It not even clear to me :-) Sure a margin is possible. Though there is even the possibility of a negative margin and different margins on every side. I imagine a Kemerer fill pattern which requires an overlapping layout and a smaller-than-bounding …
-
Hi Theo, you can disable globally by calling KLayout with the "-i" option for that purpose. Flattening is a memory-consuming operation often. Small layouts may explode to an infinite number of shapes if you're unlucky. Freezing may be an…
-
Hi, one cell doesn't make sense - you want to place different devices in different contexts, right? Then each device has to live in it's own cell which you can place individually. If you are looking for a general introduction, I'd look for a good …
-
Hi all, I stand corrected. The workaround is actually the right way to do this. The margin parameter has a different meaning. It's supposed to keep a distance to other fill cells if the cells are not on a common raster in enhanced fill mode. That …
-
Hi Theo, hierarchical, anisotropic scaling is possible, but that involves generation of variants for differently oriented cells. Right now, flattening is the only feasible option. Flattening is considerably faster if you don't chose undo support. …
-
Ah, that explains it :-) DXF is a good solution for exchanging data with AutoCAD + clones. But I'd not use it for keeping my design data. DXF does not support all use cases. If you want named layers you could consider using OASIS as the format for …
-
Hi David, You're right - exactly that's what it was meant for. I'll check why it isn't working. And the workaround is exactly what I had proposed too. Thanks for mentioning this. Matthias
-
Hi Lukas, I'm not saying it's not possible to use PCells inside PCells - if you want to place PCells inside others you can do so. I just feel it's more complicated this way. Regarding your workaround: It's a nice idea in fact. The background of t…
-
Hi David, you can subscribe to the RSS feed at the main page. It was intended to mirror the newsfeed. I hope it's working. Best regards, Matthias
-
Hi Shiriam, Maybe you can provide a screenshot (dropbox link or whatever platform you like)? A precise description of operations you perform is also helpful. Thanks, Matthias
-
Hi David, thanks for these nice pictures! This well prepared report would deserve an equally well-prepared response. But I think the solution is pretty trivial: it's a drawing bug I think. That happens always when "smooth" paths are pres…
-
Hi David, many thanks for this nice example! Best regards, Matthias
-
Hi Wing, can you paste the complete code, please? Thanks, Matthias
-
Hi Lukas, Ok, I see I'm not convincing ... :-) Here is another forum discussion with some pointers about the topic of calling PCells inside other PCells: http://klayout.de/forum/comments.php?DiscussionID=701&page=1#Item_4. Regarding your ques…
-
Hi Masaki, I had some short nights over this topic. But I think you're right and I have achieved some consolidated state now. The current implementation (going into 0.24.4) will feature * File level PROPERTY records are put before every other rec…
-
Hi Frings, I don't think you'll need scripting. Just try klayout -s 1.gds 2.gds 3.gds ... then edit the layer list using the functions from the layer list's context menu (delete, rename ..) and save the resulting layer properties to a .lyp file …
-
I wonder whether this helps against bugs too. Any experiences? Matthias
-
Hi Masaki, thanks for your analysis. Formally you're right. Although I think the BNF does not forbid using PROPERTY records after PROPNAME. But if I take 31.1 seriously then PROPERTY after PROPNAME means that the PROPERTY is associated with PROPN…
-
Hi Jack, maybe I should make the number of points a variable. To be frank I thought that 64 points for a circle are pretty smooth already. That snapping I can't explain. Maybe your input layout uses a 10nm database unit? The input's layout databas…
-
Hi Jonas, Yes, I know, that's a problem. Maybe one can re-issue the paint events lost. To me, the missing help feature is more annoying while I debug. Matthias
-
Hi Michael, thanks :-) In general, the code above is awfully old. Now there is the DRC feature which is much more convenient to use. Please see http://www.klayout.de/doc/manual/drc.html for details. But the DRC feature is also producing flat data…
-
Hi Masaki, I'm starting to get suspicious .. what exactly are you doing? So far nobody looked that deeply into the OASIS writer implementation :-) Well, never mind .. it's good you do this kind of review! I appreciate that! I shall help you by po…
-
Hi phil, I'm afraid I don't really understand your request. With a clear field mask you get glass where you have drawn something. If you have a darkfield mask you need to reverse the data. Is you request about inverting the layout for this case? …
-
Hi Frings, what do you want to do exactly? Open it for viewing or manipulation? There is a introduction into the scripting feature here: http://www.klayout.de/doc/programming/index.html. It's mainly for Ruby but there is a section about how to tra…
-
Hi Jack, To change the dimensions of your arena use "depth", "below" and "height": http://sourceforge.net/p/xsectionklayout/wiki/DocReference/#wzxhzdk12belowwzxhzdk13-wzxhzdk14depthwzxhzdk15-and-wzxhzdk16heightwzxhzdk1…