[Keith]

This is a bug – it will be fixed in 4.6.64.

A temporary workaround is to manually set the viewType for the view in the library:

lib = getLibByName("example")
view = lib.dbFindViewByName("xspice")
view.setViewType(1)

[Keith]

Hi Paco,

Is it possible to get a small example to reproduce this?

Thanks,

Keith

[Keith]

Some people have noticed that in version 4.6.62, text labels are quite small. The change was done based on a request to have the label size directly related to the label's 'height' attribute. So in that version, the label height was directly proportional to the 'height' attribute, in database units.

This is a bit small though (you may have wondered whether labels had actually disappeared), and other editors e.g. Virtuoso arbitrarily set a label with height 1.0 to be 1 micron high. So in version 4.6.63 labels will be set to an equivalent height. In the meantime a temporary workaround is to use the Display Options 'Label display scale factor' to set a scale factor for labels.

Labels in schematic/symbol views are handled differently and are scaled so they have a constant size, above a certain zoom threshold.

[Keith]

So, it turned out it was a bug in mesh generation, not Fastcap itself.

I've rebuilt v 4.6.52 and uploaded to the server, please give it a try.

[Keith]

Nothing's changed for ages – I will have a look tomorrow though.

[Keith]

v 4.6.62 is built now for Windows and Linux. Mac to follow.

[Keith]

Hi Paco,

It's just because PCells now use some of the itertools module to get the PCell argument names from the function definition.

And for some reason Python changed from having itertools as a separate module to being a builtin.

I will rebuild using the system Python only – will be version 4.6.62

regards

Keith

[Keith]

Currently there is no easy way of doing this, although it could be done via a script. I'll put it on the TODO list.

[Keith]

Hi Paco,

Yes this is a good idea, I'll put it on the TODO list.

thanks

Keith

[Keith]

Hi Paco,

I think the issue is that itertools is a builtin, the following might help:

"sys.path is only searched for Python modules. For dynamic linked
libraries,
the paths searched must be in LD_LIBRARY_PATH. Check if your
LD_LIBRARY_PATH includes /usr/local/lib, and if it doesn't, add it and
try
again."

Failing that, there are 2 options:

1) You build a Python 2.7.8 version locally and install that in /usr/local

2) I can check what Python version Ubuntu 14.04 is built with – it should be the same as the distribution, if not it can be rebuilt to use the distribution version. I had to do this on Ubuntu 18, not sure of very old versions.

[Keith]

So for normal PNG/JPG images, the rulers (and other temporary graphics like the cursor, selected set etc) are not drawn to the framebuffer.

It might be possible to change this – It's not as simple as it seems though.

[Keith]

Can you send the two netlists? I can't seem to reproduce it.

[Keith]

The code you are reaching is activated when the snap mode is diagonal only and the move delta is small. I can remove this check, the side effect is that diagonal edges may become non-diagonal.

Once again the error message can only be reached if snap mode is diagonal. Use the Display Options dialog to set the snap mode to manhattan.

[Keith]

OK well I am not sure what's going wrong for you as it works OK for me.

On a general point, if you want to work with a minimum snap size of 0.001um you need to set the dbu to more than 1000 – e.g. 5000.

[Keith]

Just checked and this effect can occur with a snap grid set to less than 5 dbu (0.005um normally). But only if the snap mode is set to diagonal.

Change your snap angle to manhattan (display options dialog) and you will not see this.

[Author]

Posts