Keith

Forum Replies Created

Viewing 15 posts - 586 through 600 (of 861 total)
  • Author
    Posts
  • in reply to: Layer name as Pcell argument #1112
    Keith
    Keymaster

    Fortunately I had some time to run the Linux builds, they are all up on the website. Version number is unchanged though.

    in reply to: Layer name as Pcell argument #1111
    Keith
    Keymaster

    The win32 and win64 builds are fixed and uploaded (still as 4.1.86). The other builds will take longer as explained.

    in reply to: Layer name as Pcell argument #1110
    Keith
    Keymaster

    Ah, now I see…

    The problem lies in the fact that the parser for the pcell args is treating the double quotes literally. So the value stored is ""metal1"" i.e. a string with double quotes surrounding the name. That's why the layer name lookup in the techfile is failing.

    I need to make a small change to the parser to correct this so that string parameters get their quotes stripped. It can be more robust than just taking off double quotes, as python is happy with single quoted strings too.

    May take a little while as I am travelling the next couple of days; a temporary workaround is to use the internal layer number as the argument – not ideal though I know.

    in reply to: Layer name as Pcell argument #1108
    Keith
    Keymaster

    Just to confirm the same works under Ubuntu 64 bit as well…

    So to confirm:

    Firstly you must import the techfile into the lib you are trying to create the pcell in before you create the pcell… else although there will be a 'techfile' it will not contain any user-defined layer names like metal1.

    Secondly, be careful not to use variables with the same names as classes, even if their case is not the same.

    regards

    Keith

    in reply to: Layer name as Pcell argument #1107
    Keith
    Keymaster

    Hi Jofre,

    2 things:

    1. Did you import a techfile into the library before using File->New Celll to create the PCell?

    2. Although in theory python should be able to distinguish between a variable called 'rect' and the class 'Rect', maybe it can't. So I tried this:

    Code:
    from ui import *

    def test_pcell(cv, mlayer="metal1") :
    lib = cv.lib()
    tech = lib.tech()
    print 'tech:', tech
    print "mlayer name:", mlayer
    layer = tech.getLayerNum(mlayer, "drawing")
    print "layer_num:", layer
    r = Rect(0, 0, 10, 10)
    cv.dbCreateRect(r, layer);
    cv.update()

    It seems to work for me on Windows, I'll try it on Linux too.

    >>> ui().fileNewCell()

    >>> tech: <ui.db_TechfilePtr; proxy of C++ db_Techfile instance at _20001007_p_db_Techfile>
    mlayer name: metal1
    layer_num: 6
    # INFO: Reading preferences file C:/Users/keith/.gladerc

    >>> # INFO: Opened cell test_pcell view layout
    regards
    Keith


    in reply to: Glade for Mac OSX #1102
    Keith
    Keymaster

    Glade is coming to Mac OSX in the near future. Can't say exactly when but the hardware and software has been acquired!

    in reply to: Download stats #1101
    Keith
    Keymaster

    Just for people's interest, here's a quick summary of the last 100 downloads:

    glade4_win32 41
    glade4_win64 26
    glade4_linux64_rh5 9
    glade4_linux32_ub10 7
    glade4_linux32_rh5 4
    glade4_linux64_ub10 3
    glade4_linux64_rh4 3
    glade4_linux32_rh4 3
    spice3f5_win32 2
    spice3f5_win64 1
    glade4_sunos 1

    Naturally the numbers vary over time, with 64 bit Windows showing a strong growth, probably due to most PCs shipping today with Windows64 as standard.

    in reply to: Glade on ANDROID #1100
    Keith
    Keymaster

    If and when the Qt gui toolkit supports Android, it might just be possible.

    However, I doubt that is ever going to happen.

    I did wonder about having such an application run on iOS so I could use it on an iPad, but (a) the user interface is going to be a problem (b) memory is going to be a problem and (c) getting data in/out is going to be a problem.

    Let's stick to what is possible, yes?

    in reply to: hierarchical pcells #1098
    Keith
    Keymaster

    Sure – sponsor me with $1m and i'll certainly consider it.

    in reply to: Help Menu should have links #1097
    Keith
    Keymaster

    The legal disclaimer is in the README.txt file in the distribuition. You did read this, didn't you?

    in reply to: hierarchical pcells #1090
    Keith
    Keymaster

    Unlikely to happen in the near future, sorry. This is freeware!

    in reply to: Boxed zoom #1089
    Keith
    Keymaster

    Sorry, I'm still not understanding why you are having problems with zooming.

    Right-dragging the mouse zooms in or out according to the box that is drawn as you drag the mouse.

    Drag from lower left to upper right and you will zoom in to the boxed area you draw.

    Drag from upper left to lower left will zoom out from the box area according to the ratio of box size to screen size – a small box will mean you zoom out a long way, less so with a larger box.

    Or use the z / shift-Z bindkeys to zoom in/out.

    The right mouse mode can now be configured in the display options dialog to be either like Cadence Virtuoso (right mouse button zooms in only), Glade (right mouse zooms in & out) or a special mode where right mouse can zoom in/out or fit the window.

    in reply to: Help Menu should have links #1088
    Keith
    Keymaster

    What links in the Help menu are you thinking about? Or do you mean links in the help documentation itself?

    As for license info, the product is unlicensed. It says it's freeware on the download page…

    Finally, yes, having a mailto: link on the about box is a good idea. I'll need to implement a custom dialog to do that though, as a simple QMessageBox does not support rich text.

    in reply to: X errors showing up for Move dialog #1084
    Keith
    Keymaster

    Hi Bill,

    No, you can select edges or vertices in 'partial' mode. You need to select it near the vertex (within 10% of the edge length).

    If this is not working for you, please let me know exactly what you are trying, so I can try and reproduce it.

    – Keith

    in reply to: X errors showing up for Move dialog #1081
    Keith
    Keymaster

    Hi Bill,

    If it's using OpenGL you will see lines like:

    # OpenGL vendor: NVIDIA Corporation

    # OpenGL renderer: Quadro 600/PCI/SSE2
    # OpenGL version: 4.1.0
    # OpenGL FBOs will be used.

    Without those, it's not using OpenGL (hence no layer transparency, although you can get this by using the 'Opacity' slider to make layers part transparent even without OpenGL, at some cost of rendering speed).

    There are only 2 reasons why it would not use OpenGL,
    1. If you have the env var GLADE_USE_OPENGL persisting somehow.
    2. If Qt tests for FBOs and pbuffers both fail. Glade writes to an offscreen buffer which is then texture mapped to the display.

    Does it do the same with the RH5 version?

    Also, some version of Linux require you to explicitly turn on hardware accelerated display. It might be work checking if this is the case on your machine.

    Lastly, if you're running on a server and displaying remotely though e.g.VNC it won't work unless your VNC supports OpenGL; also if you are using VMWare to run a Linux guest OS on e.g. a Windows host it won't work, although I hear that VMWare and NVidia are working on something that will make this work… one day.

    – Keith

Viewing 15 posts - 586 through 600 (of 861 total)