Trial #2 ==>using add_pcell_variant method : this crashes the whole klayout

#268c6b

3. loop #1 & #2 until got all layer

Hi

3. size up #2 by 0.18 (as an one of the output)

3. Run DRC and LVS to validate the change of #1 & #2, to fulfill foundry B design rule.

area of each green and blue polygon.(At #1, #2, #3)

Issue #289 is on Github already, but I thought discussing it in the forum as well might be a good idea.

I have created GitHub #203 to track this issue.

Hi Matthias,

I am trying to access GDSII user properties through Python script. When I open gds file containing USERPROP and USERATTR records I can see in object properties that it has for example property #2 with

You can report bug and search the issue database on GitHub: https://github.com/klayoutmatthias/klayout/issues?utf8=%E2%9C%93&q=is%3Aissue. Yours are #24 and #48.

3. Delete layer 4/0 (or any other layer not in the group defined in #2)

#2 0x0000000001688a0a in delete_garbage (generation=2, n_collected=0x0, n_uncollectable=0x0, nofail=1) at Modules/gcmodule.c:867

Regarding #2, I think you may have the wrong format (meaning, it might not be (,;,; ... ). There might be different separators, or it might need spaces, or something. Having never used it for a PCell

Anyway, it might be easier to stick with the regular "tech" approach you already have (file #1), and a separate GDS (file #2) which the user would have to figure out how to place in

0x00002aaab29b5182 in __smokeqtgui::x_QApplication::~x_QApplication() () from /usr/pack/qt4-qtruby-2.2.0-di/x86_64-Linux-2.6/lib/libsmokeqtgui.so.3#3 0x00002aaab29abf75 in __smokeqtgui::xcall_QAppl

* Use case #2: A user writes (or multiple users collaborate on) a larger script or a collection of scripts.

practically, you would start drawing polygon #2 inside whatever cell polygon #1 is). Then, if the cell of interest is not already in bold text inin the tree on the left, right-click on the cell and

Just go with #2. For that you need to: