Forum Replies Created
-
Posts
-
Can you send any data to reproduce the crash? There were a few changes recently to geomConnect to fix some other bugs.
Yes, in version 4.1.27 and later Glade will ready a startup file called '.glade.py' in the directory given by the env var HOME.
For Linux/Solaris this is just ~/.glade.py
For Windows, you need to explicitly set the HOME env var to the directory you want to call home (for me C:Userskeith)
I'd be interested in what are the top 5 new features people would like to see in Glade. Either post in this thread, PM or email. Thanks!
You probably had the display options dialog 'Show Labels' button turned off.
When you create a new label in the gui, this option is automatically turned on, hence you'd see the other labels again.
I've added some UI wrappers that allow creating toolbars and setting icons for their buttons. This is in the 4.1.27 version; please see the UI docs for details.
BTW, stretching more than 1 edge/vertex can give odd results. This is something that is to be fixed, hopefully in 4.1.27.
Well you can currently add menus, submenus and menu items that trigger actions. You can also define bindkeys (shortcuts) that trigger actions. And actions of course can be linked to user defined python functions – see the ui() python documentation in the docs (under 'Programming Glade in Python').
By button, do you mean toolbar buttons? I guess it would be possible to add functions to create and add toolbars, and buttons to those toolbars associated with an action. Would you want to create icons for the buttons?
No picture?
Shield top/bottom seems to work for me OK, using the 'example.tch' techfile. Note that the techfile must contain layer function keywords for all the layers, in the correct order so that a routing layer above and below the current layer can be found – else no top/bottom layer will be added.
By popular request, the latest version removes the 6 month timeout that requires users to download a newer version of Glade. It will still nag you with a dialog box to download a later version, but will function completely normally if you choose to ignore this warning.
Various other minor fixes have been made, please see the Changes file.
'Show Used Layers' was only setting the layers used in the current cellView, which probably accounts for your missing layers. As of version 4.1.26 it now looks at all the hierarchy and adds all layers found to the used layers.
Ah, you've found a bug. The library combobox in the Import Cadence techfile dialog was not editable. I'll change that.
I've not used Windows 7, only Vista and before.
On e.g. Vista, right click on 'My Computer' icon or go to the control panel and click on 'System'.
In the top left of the form under 'Tasks', click on 'Advanced System Settings'. This brings up a dialog entitled 'System Properties'. In the bottom right you'll find a button 'Environment Variables…'. Click on it.
This brings up a dialog 'Environment Variables'. You can add Glade env vars to the 'User Variables' section.
You don't need to set ANY env vars to use Glade, however to use the online documentation GLADE_HOME needs to be set to where you unzipped the files to, i.e. the directory path containing the 'html' subdirectory.
So if you installed Glade to e.g.
C:UsersFredStuff
then set GLADE_HOME to the above path.
There are a few other potentially useful env vars:
GLADE_DRC_FILE – sets the default python drc file used when you use the command Verify->DRC->Run…
GLADE_EXT_FILE – the same, but for Verify->Extract->Run…
GLADE_USE_OPENGL – set to 'no' if you do not want to use OpenGL. Don't set this variable if you do want to use OpenGL.
GLADE_NO_EXCEPTION_HANDLER – disables the global exception handler. Sometimes useful when tracking down crashes, as the resulting crash dump may contain useful info.
Lastly you mention you didn't need to use the vcredist_x64.exe installer – this may not be required if your machine already has the Microsoft C++ runtime redistributables installed. See e.g. http://www.microsoft.com/downloads/en/details.aspx?familyid=ba9257ca-337f-4b40-8c14-157cfdffee4e&displaylang=en
You don't need to export a Glade techfile. Maybe it's not clear, but you almost never need to create a library explicitly – this is done automatically when you either import a techfile (Cadence, Laker or Glade techfiles) or if you import GDS without a techfile.
So the two steps are:
– import the Cadence techfile. You specify the library name to import into; this will get created if it does not exist. The library name defaults to "default" but you can type any name you want into the 'Into Library' field.
– Import your GDS. Use the library name specified in the previous step.
