Matthias
About
- Username
- Matthias
- Joined
- Visits
- 16
- Last Active
- Roles
- Member
Comments
-
Hi Jo, I had a report of a similar issue before: [http://klayout.de/forum/comments.php?DiscussionID=98&page=1#Item_9]. That case apparently was related to the native file dialog, which was GTk. My suggestion was to try with a different style, …
-
The link is working again.
-
Hi Jimmy, that is very good input. Thanks for the analysis. In fact, you're right. There is something different with respect to the zlib. For 0.21 I was including a copy of the code (zlib 1.2.5). This way it was much more convenient to build on Wi…
-
Hi Jimmy, One thing that has changed is the handling of UTF8 encoding locales. But that should make it better, not worse. In the case of GDS files, the reader uses the zlib which I assume is active in your case. I am not aware that zlib is encoding…
-
Hi Jimmy, that is really weired. There should not be any difference in GDS files saved by this or other versions. The error message indicates that there is something very basic wrong, like something with the fopen function. Are you able to open t…
-
Hi Jimmy, the QFrame constructor mentioned in the error message is a special one which is only provided if the code is compiled with -DQT3_SUPPORT (which is the case) and the Qt library is built with Qt3 support. Usually that is the case but depend…
-
Hi Jimmy, I am not quite familiar with MacOS builds (I don't make the MacOS binaries myself), but I found one post which describes a similar problem here: http://www.cocoaforge.com/viewtopic.php?f=6&t=21261 Frankly I don't quite understand wh…
-
Hallo, you're right, the two tools serve the same purpose. However, there is a important difference: The XOR tool performs a comparison of the merged polygons as seen from the top cell. This basically verifies the equivalence of two layouts in th…
-
Hi Werd, I admit, I am somewhat helpless now. I am quite sure (from your stack trace) that the problem is related to QGtkStyle, but I can't reproduce it, even after explicitly enabling GTK style. What puzzles me is that this style is supposed to w…
-
Hi, thank you for the stack trace. It indicates that the problem happens inside GTK's file dialog and does not seem to be related to Qt or KLayout at the first glance. Google gave me some hint that libxml2 might be the problem (https://bugs.launch…
-
Hi, you can create a stack trace with the GNU debugger (gdb) for example. It usually comes with the gcc package, so I assume you have it already. Instead of starting KLayout directly, enter gdb cd {where klayout resides}gdb ./klayout on the gdb …
-
Hi, the logs look OK as well as the package list. I assume that gcc 4.4.0 is in your path. The Qt package is somewhat outdated - the oldest one I am testing on is 4.2.3. Although not a lot Qt-related code has changed to 0.21, I had issues with some…
-
Hi Ray, meanwhile I made some experiments with TrueView myself. You're right that it's somewhat more picky than other viewers. Since it delivers some meaningful error messages I was able to change the DXF writer accordingly. Right now, I don't have…
-
Hi Ray, line 22 is always the first entry in the layer table. More precisely that is the layer name (as the message says). When I export GDS (or another format using numbers for layers) to DXF I create layer names of the form LxDy where x is the l…
-
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…