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 Chris,
This really is a long post. Here are some answers:
1.) you're probably not doing something wrong. I'm not aware that drop-down list changes would trigger callbacks. That's kind of questionable as the contract is that layout won't change …
Hi,
I see I need to explain the concept here. The main difference between 0.25.x and 0.24.10 was a cleaner type system of geometrical primitive types.
One concept is that of vector vs. point (see https://www.klayout.de/doc-qt4/programming/geometry…
Hi,
you can try using "region_a.merged_semantics = false". This should leave the shapes unmerged.
But regions are collections of polygons and everything will be polygonized. If you want to the other shape types such as paths your code is…
Hi,
yes, exactly this is the right way to do it :-)
I did not know about "next(...)". Thanks for this sample. This looks pretty useful.
Regards,
Matthias
Hi,
sorry for the delayed reply.
Your solution isn't bad although I'd say the Ruby loop is probably going to be a bit slow.
The solution I'd suggest is to use Region objects. Regions are the basic building blocks of DRC scripts and they provide a…
Hi,
a plugin is a tool option - if the plugin is active, it will take full control over the mouse. Hence you cannot have both select mode and your own tool feature while the plugin is active.
The net tracer's approach is to grab the mouse and rele…
Hallo,
Here is some sample script (Python). With other values, but the comments should make it easy to adjust the script:
# fetches current layout view and cell viewview = pya.LayoutView.current()cellview = pya.CellView.active()# gets the correspo…
Hi Oscar,
Both
pya.DPolygon.ellipse(pya.DBox.new(-1,-5,1,5),170).num_points()pya.DPolygon.ellipse(pya.DBox.new(-0.1,-5,0.1,5),170).num_points()
give 170, so the polygons are fine.
But maybe your should check your database unit. That's the minimu…
Hi chhung,
looks like __int128 is lacking. This is essential for 64bit coordinate support, so you cannot skip this.
__int128 is present on gcc >= 4.6. According to the documentation on gcc >= 4.1, you can substitute "__int128" by &…
Hi chhung,
-with-64bit-coord is the right option.
But please try to build 0.25.x or the master branch of GitHub. 0.24.10 is not tested for 64bit builds and is pretty outdated now.
Kind regards,
Matthias
Hi,
I'm sorry, but I can't say anything about LayoutEditor. Is your goal to develop an algorithm or to integrate LayoutEditor's router? AFAIK LayoutEditor isn't GPL, so integration probably isn't an option.
Matthias
Hi chhung,
I guess that the coordinate space of this file exceeds the 32bit precision KLayout is built with by default. You can enable 64bit coordinate support, but you'll have to build KLayout yourself or ask someone to do it. As 64 bit coordinate…
Hi,
I tried to reproduce the issue, but I cannot fully confirm your observations.
What I see is (0.25.8):
* when I unselect "write PCell information" and only write "visible layers", only these layers will appear in the file.
…
Hi Ken,
There is a vision, but a vision is a plan that maybe dosn't get realized :-)
I'm simply not enough people. A clone procedure would be helpful.
Fun aside, I'm seeing some schematic editors around. Maybe there is a chance to plug one of the…
Hi vikas,
That's not good. But to be frank, I'm not really up to date with the MacOS distribution. I'm not providing this myself as I'm not a Mac user.
Matthias
Thanks for the bug report on GitHub! It looks like an issue with the Python iterator protocol (or the way I understand that). I'll take care of this.
Kind regards,
Matthias
Yes, there are two modes :-)
On Windows you'll get three start menu icons: a default (the one you configured in Application/Editing mode), a viewer and an editor mode.
On Linux (and Windows) with "klayout" you get default mode. With &quo…
Hi Dave,
the usual way to making Ruby find a file next to another is to use:
inst_dir = File.dirname(__FILE__)$:.member?(file_dir) || $:.push(inst_dir)require "NumLib.rb"
Matthias
Hi Ken,
There is a nice answer to this question (the title is misspelled, so it's hard to find):
https://www.klayout.de/forum/discussion/598/cut-polygons
In short, the answer is "partial edit mode".
Matthias
Hi Olivier,
there is a related post here: https://www.klayout.de/forum/discussion/1175/extract-information-from-oasis-file#latest
It's basically the same question.
Regards,
Matthias
Hi Ken,
strange indeed ... but I see you as "KenShawSkorpios" now :-)
Maybe you can try "enclosing". That should do the job. The name is slightly misleading: enclosing does not ensure one layer actually encloses another, but it…
Very good :-)
KLayout core development is C++ - no Python involved.
For Python scripts you basically have many options. You can provide packages or Python scripts based on the standalone klayout module (see klayout on PyPI). I don't have specific …
Hi Luciano,
you can zip files for attaching them.
Anyway - don't use SourceForge anymore. Just install the xsection package (in Tools/Package Manager). Maintenance happens on GitHub (https://github.com/klayoutmatthias/xsection).
For your issue, t…
BTW: texts can be generated without basic lib using "TextGenerator". There was a similar issue with this, but that should be fixed (https://github.com/KLayout/klayout/issues/241).
Hi Clemens,
it's built-in in the main application, so you can't load it directly. I'll need to debug the reason it's not there. The ticket is: https://github.com/KLayout/klayout/issues/252
Thanks for reporting this,
Matthias