[Keith]

'glade -v' should just print the Glade version, and then exit.

The python interpreter is embedded into Glade and called via C++; Glade is not a Python app, so the normal -v for traceback doesn't work, or at least was never intended to work…

[Keith]

The initial build of 4.3.0 had a couple of bugs:

– ActiveState python v2.7 on Linux seems to be broken
– A bug in DRC causing a crash
– Error opening a previously saved library.

These have been fixed and the build process started. Expect all platforms except Solaris to have a stable 4.3.0 build by about 16:00 GMT on 6th (today).

[Keith]

Thanks for pointing this out. It seems the AS 2.7.2 python is bad somehow, as reverting to the previous 2.6 version (used in earlier versions of Glade) works fine.

Version 4.3.0 will have the fix.

[Keith]

Version 4.2.7 is out and fixes several niggling problems entering data ongrid especially for manhattan shapes. In particular paths and polygons have more rigorous checking that they are manhattan, if manhattan entry mode was selected.

The next release may take a little while as there is some new functionality planned which needs far-rreaching changes in the database, graphics and IO handling…

[Keith]

I have not really looked at these platforms but I use the commercial version of Qt from Trolltech/Nokia/Digia. Neither Android nor iOS is officially supported by them AFAIK.

The real problem is that the gui use model on e.g. a tablet is very different to a traditional PC. Assuming the hardware can support it (i.e. enough virtual memory etc), the problem is that yes, you could load and draw e.g. some GDS2. You could even zoom and pan. But then how to control hierarchy display, move between levels of hierarchy, select and query objects? Given that most EDA tools rely on some form of scripting to set up commonly used settings, I don't see how it would work in a usable environment. Hence I agree with your comment that it wouldn't be very useful…

[Keith]

Latest build is up on the ftp site now. All builds except Solaris (which takes a long long time these days…).

Includes enhancements and bugfixes requested by users – thanks for reporting them!

Edit: There was a bug in the DRC code in the initial build of this version. This was fixed as of the 20th (Sunday). If you downloaded 4.2.5 before the 20th, please download again.

[Keith]

One thing worth checking is the version of Python on your Mac. Glade was built linked to version 2.7, it's possible you have an older version and that is causing a problem.

[Keith]

Hi Matt,

Any more info or error messages to debug this? I am building on Lion, but alas have no means to build or test on older versions of the OS. From what I was led to believe by the Trolltech/Nokia/Digia folks, this would be compatible (from a Qt point of view) with OS's from 10.5 onwards.

cheers

Keith

[Keith]

If you want to import DXF and export it to GDS2, you will need to map the DXF layers to GDS layer number/datatypes.

So create a tech file with the DXF layer names and the GDS layer numbers/datatypes for those layers. Import this first, then import the DXF.

Then you can export GDS and the layers will be written to GDS2 as specified in the tech file.

Hope this helps,

Keith

[Keith]

The latest version 4.2.3 fixes some library issues with Qt on the Mac OS X platform. Some cosmetic enhancements have been made to the dialogs specifically for the Mac, and finally some bugs in import/export DXF have been fixed.

[Keith]

Hi Perokichimoch,

Currently when a DXF layer is read in, its name is checked against names defined by the library's techfile. If a layer of the same name exists, then the DXF layer is set to the same layer.

However, there seems to be a bug at the moment in that the GDS layer defined in the techfile is being overwritten with the layer number of the layer found. This should not be the case, so I'll fix that bug in the next release.

regards

Keith

[Keith]

If anyone's tried to register recently and not yet got approval, please try again as a problem with the forum meant that some user registrations failed.

[Keith]

Initial Mac OSX port has been done and is available on the web page. There are some missing capabilities which will be added in the near future but the basics are all there, I hope.

I'd appreciate any feedback on any problems as it's hard to tell if the app is correct without testing on a machine without installed Qt and Python libs.

BTW this version is 64 bit and should run on OSX 10.5 up.

[Keith]

Have you set the PYTHONPATH env var to point to the directory that contains the Glade installation .py files?

Python searches for modules to load according to PYTHONPATH in much the same way as your OS looks for executables in PATH.

[Keith]

If you export the techfile using File->Export Techfile… it will save a techfile with the layers/display info in Glade format.

Then edit a file called .glade.py in your home directory (In windows you need to explicitly set the HOME env var to this directory, on Linux just use ~/.glade.py)

In it put the following (replace strings with what you want):

from ui import *
ui().importTech("libName", "C:/Users/keith/example.tch")

Then the techfile will get loaded every time Glade starts up.

[Author]

Posts