Forum Replies Created
-
AuthorPosts
-
Keith
KeymasterWhat OS was used on each computer – were they different?
What version of Glade was used on each? Were they differerent?
What sort of 'layout' was copied? GDS2? A Glade library? Be more specific.
If e.g GDS2 was copied, did you load identical techfiles before loading the Gds2?
Without more detailed info on *exactly* what you did its impossible to answer.Keith
KeymasterThe full 4.3.2 version is now available as of today (15th)
Keith
KeymasterOK this is now implemented in 4.3.2 which is available on most platforms today (15th).
Keith
KeymasterCurrently the only thing you can do is to select all texts on the TEXT layer, and change their magnification to a larger value. I'll see if I can put an option on the Import LEF dialog to allow user specified text height.
I guess this is not for std cells, where the default seems to work quite well?
Keith
KeymasterI don't see a crash. I do see an issue where if you try to zoom in past the database resolution (typically 0.001um) then zooming out does nothing, only window fit restores the view. This is because the view height/width goes to zero, and so zooming (which scales the view) does nothing. This is easy enough to fix.
But I don't see any crash. Did you get a crash dump?
Keith
KeymasterThis is fixed in the windows patch 4.3.1.1 and will be a full release soon in 4.3.2.
Keith
KeymasterPlease send logfile.
In general, when reporting a bug, send at least the logfile header so we can see:
– what platform you're running on and what OS
– version of Glade the crash occurred on
– graphics subsystem used.
Keith
KeymasterSorry, your attachment went somewhere… but didn't arrive here. Please email to support@peardrop.co.uk.
Also please when reporting bugs post the header of the logfile so I can see:
– what platform you're running on and what OS
– version of Glade the crash occurred on
– graphics subsystem used.Thaks,
Keith
Keith
KeymasterWell if you have VC++, run it, start Glade and attach the debugger to the process. Then send me the stack trace when it crashes.
Keith
KeymasterWell, with the latest build on a vanilla Windows 7 32 bit laptop, I get no crash. You did install the VC++ runtime DLLs? Although I wouln't expect it to even load without them.
Keith
KeymasterLog files? Crash dumps?
I find it hard to fix some bugs as i'm not telepathic!
Keith
KeymasterAh, I have located the problem. The win32 version was missing the file 'types.py' (it is present in the win64 version). Without that, or a valid Python installation on your PC with 'types.py' in your PYTHONPATH, import ui failed.
I have fixed the distribution win32 version and uploaded it to the website.
Keith
KeymasterHard to say without further info. Make sure you delete any .pyc files from the installation, in case they are from a previous version. Or try installing in a different directory.
Keith
KeymasterFew things:
1) I assume you installed Glade at
glade4_win32 and set the environment variable %GLADE_HOME% to this dir, and %PYTHONPATH% so the same dir.
2) Do you have write permission to this directory? Is there the ui.py file in this directory, and is it readable?
3) Check that you are not running one version of Glade and pointing PYTHONPATH at another version of the ui.py file. This will also give the error you see.
Also I'd recommend downloading the latest 4.3.1 build, as there were a few issues with 4.2.7/4.3.0.
regards
Keith
Keith
KeymasterI think you can get the equivalent of the cmd line 'python -v' option by using an environment variable, according to the documentation:
PYTHONVERBOSE
If this is set to a non-empty string it is equivalent to specifying the -v
option. If set to an integer, it is equivalent to specifying -v
multiple times.
But yes, as you say, if Glade crashes then it displays a window with crash dump info on all platforms except Solaris. The idea being that if you want to submit a bug, the crash dump info can be used to trace what went wrong, in the absence of a reproducible test case. -
AuthorPosts